Skip to content

Add PushSubscription.expirationTime#248

Merged
beverloo merged 1 commit into
w3c:gh-pagesfrom
beverloo:expirationTime
Apr 18, 2017
Merged

Add PushSubscription.expirationTime#248
beverloo merged 1 commit into
w3c:gh-pagesfrom
beverloo:expirationTime

Conversation

@beverloo
Copy link
Copy Markdown
Member

The expiration time of a push subscription indicates the time, in
milliseconds since the UNIX epoch (UTC), at which the subscription will
be deactivated.

This is an important addition for user agents that refresh their
subscriptions, as it gives the developer knowledge of a final time after
which they can garbage collect the stored subscriptions if the user has
not communicated the details of the refreshed subscription.

Fixes #86

@beverloo beverloo requested a review from martinthomson April 11, 2017 22:05
Comment thread index.html
<p>
A <a>push subscription</a> MAY have an associated <dfn>subscription expiration time</dfn>.
When set, it MUST be the time, in milliseconds since 00:00:00 UTC on 1 January 1970,
at which the subscription will be <a>deactivated</a>. The <a>user agent</a> SHOULD attempt
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/to/the

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done - thanks!

The expiration time of a push subscription indicates the time, in
milliseconds since the UNIX epoch (UTC), at which the subscription will
be deactivated.

This is an important addition for user agents that refresh their
subscriptions, as it gives the developer knowledge of a final time after
which they can garbage collect the stored subscriptions if the user has
not communicated the details of the refreshed subscription.

Fixes w3c#86
@beverloo beverloo merged commit 73da641 into w3c:gh-pages Apr 18, 2017
perosb added a commit to perosb/home-assistant that referenced this pull request Jun 4, 2017
Enabled by default in Chrome 60.
Only accepts the param, doesn't act on the actual expiration date. Chrome will always pass NULL for now.

w3c/push-api#248
https://www.chromestatus.com/feature/4929396687241216
https://bugs.chromium.org/p/chromium/issues/detail?id=718837
balloob pushed a commit to home-assistant/core that referenced this pull request Jun 5, 2017
Enabled by default in Chrome 60.
Only accepts the param, doesn't act on the actual expiration date. Chrome will always pass NULL for now.

w3c/push-api#248
https://www.chromestatus.com/feature/4929396687241216
https://bugs.chromium.org/p/chromium/issues/detail?id=718837
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants