Re: [w3c/push-api] Make PushSubscription.expirationTime mandatory (#302)

I agree that there are two strategies here:

1. Making the PushSubscription.expirationTime mandatory allows the _application server_ to safely delete old endpoints in case the push service forgets to do it
2. The browser _push service_ should detect inactive devices and mark the endpoint as expired (i.e. return 410 Gone to the application server)

However none of them is enforced by the standard at the moment. I think that at least one should be enforced by the standard in order to avoid future problems. Also, the two strategies can coexist: if a browser decides to implement both that would be great.

-- 
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/302#issuecomment-435157738

Received on Thursday, 1 November 2018 19:30:42 UTC