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

@mohamedhafez You bring up a good point, and I think it's relevant for the other cases, too. We don't want developers rolling their own backoff and retry logic for `pushsubscriptionchange`, and a web hook is in line with features like the CSP error reporting mechanism.

Another approach is for the browser is to retrigger `pushsubscriptionchange` with exponential backoff if the promise passed to `pushSubscriptionChangeEvent.waitUntil()` rejects. That way, scripts could implement logic for updating local state, too. Though, unscrupulous sites could game it by returning a rejected promise so that the worker periodically wakes up in the background.

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