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

Those challenges (availability of battery, CPU, memory, network, device being on at all) are real. Most of these apply to any solution of course.

I think there is also an argument in favor of `pushsubscriptionchange`: the user agent controls when to fire it. As the user agent knows more about the state of the device and its resources, it can select a more suitable time to refresh the subscription. The event can also be fired more than once, in case refresh failed.

A second advantage of the event based approach is that it can be run in the background, at a time when the app would otherwise not be running at all.

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