Re: [w3c/push-api] pushsubscriptionchange - Initial feedback (#120)

PR #234 defined this in a new `Subscription Refreshes` section. We suggest using background sync for getting the updated details to your server (which has yet to be changed), and don't _require_ the old subscription to be immediately invalidated exactly to allow for a brief window during which the change can propagate.

-- 
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/120#issuecomment-280742172

Received on Friday, 17 February 2017 19:22:55 UTC