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

Specifically regarding the situation when a subscription needs to be refreshed, for no other reason than that the user has been subscribed for a long time, I'm worried about failures interrupting service for long term users that depend on the notifications. What if theres a network error when `pushsubscriptionchange` gets called? Every developer that wanted to ensure their service was reliable could put in code to catch that and then retry, but that seems like a lot of people repeating the same work, and probably getting it wrong half the time. The result would be a poorer end-user experience.

Perhaps there could be an option for the serviceworker to specify a URL to hit in order to notify a server of the refresh, that would automatically get retried for a few days until it got a 200 response? And both the old subscription and new subscription could remain valid until the server responded with a 200 so we are sure it knows about the change, at which point the old subscription could be invalidated?

---
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-225075199