[dispatch] =?UTF-8?Q?Re:__Potential_incoming_work:_web_push_for_IMAP, _Cal?= DAV and CardDAV

["Bron Gondwana" <[e-mail]>]

On Sat, Oct 26, 2019, at 07:14, Michael Toomim wrote:
> I think we can gain a lot by putting this standard *into* basic HTTP, rather than building layers on top. By adding Synchronization to HTTP, we get the functionality of Web Push, but it can be implemented automatically, for all resources, without any extra effort from the programmer. The whole web has changed in the last 20 years— from static pages to dynamic data —and it's time we upgrade the protocol at a deep level. Getting a notification of a message on your phone shouldn't be any different from getting the actual message in the app.

At this point the big difference is whether you want a push of the entire resource, or (as JMAP does) an edge trigger to say "there's something new of this object type on the server - issue a query about which bits you're interested in to see if there's anything new you want to fetch".

At which point the granularity of detail becomes interesting - because you only want to be informed of changes if there's a high probability that they are things you are interested in, and even more so - if there's a high probability that you'll be able to see them! You don't want a push every time a resource on a server with a million users changes if you can only see your own resources!

We do that on our own server with pushing you every change to you own resources plus doing ACL filtering to see if any other user can see the resources and giving them an ACL push too, even if they aren't subscribed to the resources and won't notice a change.... so there could be more smarts in the push filter but it seems to balance out OK in a real life, just the occasional extra wake. And we separate data types like email and calendar into separate change pools.

Bron.

--
 Bron Gondwana, CEO, Fastmail Pty Ltd
 [e-mail]