Re: [push-api] PushSubscription should have an attribute for ExpirationTime (#86)

If a subscription expires while a device is offline, it can always learn about the event when it wakes up.

If we assume some sort of session-based interaction between the UA and push service, then re-establishing that session after a long period offline is common.  At that point, the push service can inform the UA of the absent session.  That provides a pretty good trigger for UA-based refresh and any necessary events.

All that an expiration time does here is reduce the number of attempts from the application server to request pushes.  But that number can always be reduced to one by having the push subscription endpoint return a terminal error code (like 410 Gone).

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/86#issuecomment-70757926