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

I think the fundamental question to us is still whether the refresh can be guaranteed at all time and whether the expirationTime can help.  So, let's focus on a special case for now.

The target device is off or out of network so there is no guarantee that it will receive the expiration message from the push server.  There is a blackout period before the subscription is refreshed completely.

I see at least 2 possible solutions.  One is to expose the expirationTime so the webapp can refresh accordingly.  The other is to keep a hidden expirationTime (as Michael mentioned) and fire event by the user agent, of course there is a question when to fire since the user agent doesn't know whether the expiration message is lost or not.  The first option seems better to me.  But, please feel free to expand here and add other solutions you might have in mind.

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