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

Now that we define the concept of refreshing a subscription, I think it's worth to consider this again because this property would now be entirely informative.

The main argument I can come up with for this property is to enable developers to include a hard date in their data store after which a subscription should not be considered anymore (_time of deactivation_). That has good value for relatively little cost.

Assuming we define `expirationTime` as the time of deactivateion, would it confuse developers if a user agent fires `pushsubscriptionchange` at an earlier time to allow for some overlap? 

The property would definitely need to be nullable, since not every push service will care about expiration, or be in a position at which they can indicate this. That's probably OK.

-- 
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/86#issuecomment-280750287