Re: [w3c/push-api] Fire pushsubscriptionchange when user revokes permission (#116)

@kitcambridge You've got the point. 
If the server has to **manage that scenario as an exception** is not a problem. However it's an exception, not the normal flow: statistically it would be a great improvement. Moreover I think that most of the time when a user unsubscribes has the browser open and probably is not offline.

However I'm not convinced by the sequence you have described: you say that the token has expired and the push service returns 404 to the application server. That's not possible if the browser is offline. If the user unsubscribes when he's offline neither the push service nor the app server can be informed: they'll be informed at the same time when the user connects to the internet. So I think that **you'll never get 404 from the push service for this scenario**.


---
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/116#issuecomment-221505726