Re: [dispatch] Potential incoming work: web push for IMAP, CalDAV and CardDAV

[Michael Toomim <[e-mail]>]

Julian:
> And the end of the day, this is still HTTP. The response needs a media
> type that describes the payload. You are defining a new payload format
> that can handle multiple resources, so you need a container-like format.
> multipart can do that, but I agree the mail format legacy with the
> boundary string is sub optimal.

Ah, yes-- that *is* what we are doing.  Thank you for articulating it nicely!

> But then, sending Content-Length inside the payload is a bit weird as
> well; it defeats streaming the part; you may want to consider a binary
> container format instead (based on HTTP chunked, for instance).

Ah, yes.  Well, you can still stream updates here by breaking up a single change into multiple patches.  Then each patch can occupy a different message.  You can make them as small as you'd like; you'll only face the overload of an extra frame header in http/2.

I'm cc'ing the braid list, in case they are interested. [Thread link] <https://mailarchive.ietf.org/arch/msg/dispatch/gU2cWDGgxc-1O1xAubdIxNeeo58>