Re: [w3c/push-api] Describe process for subscription updates (#132)

There are no good solutions here without perfect prescience.  The browser should (and probably will) notify in advance of expiration events.  Though I don't believe that anyone plans these things enough in advance that we will have a usable warning (or that we will bother to build mechanisms to support that advance warning).  More likely, we will only break a subscription rarely, but accept the outage when we do.

I say this on the basis that a wholly reliable push service is not something that applications should expect.  I don't know what the actual numbers are, but I've heard reports that even the best-performing push services are not reliable enough to use as the sole means of synchronizing application state.  So applications will always have to have ways to deal with desynchronization.

The [background sync API](https://wicg.github.io/BackgroundSync/spec/) in its more complete incarnation is a better answer for the robustness issue, I think.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/132#issuecomment-225437896