Re: [w3c/push-api] Pass removed subscriptions as a property of the `pushsubscriptionchange` event (#193)

Huge +1: right now a subscription endpoint in essence acts as the 'ID' of a push target. Developers are frequently going to be saving state on their app server associated with that push target ID, e.g. "this push target ID belongs to this user". If the push target ID is going to change that's all good, but any long-term service is going to have to be able to tell its app server "hey, this old ID should now be known as this new ID"

If the `pushsubscriptionchange` event came with two attributes, `oldSubscription` AND `newSubscription`, I think its meaning would be obvious and could be summed up in one simple phrase: _oldSubscription is being replaced with newSubscription. Let your app server know_.

---
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/193#issuecomment-225326891