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

Hi! So in VAPID `subscription.endpoint` has unique id. Can that (or should?) be reliably used to identify devices? Example:

1. Device subscribed -- subscription stored on the server with subscript/endpoint as primary key
2. Device got new subscription, `pushsubscriptionchange` fired with old/new subscription
3. ServiceWorker sends to the server 2 subscription info: old one and the new one to replace with

Can server rely on unique endpoint here to performing matching and replace the old subscription with the new one? Or having custom UUID / cookie session is the way to go here?

Thanks.

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