On Thursday, October 23, 2014 9:16 AM, Costin Manolache wrote:
On Wed, Oct 22, 2014 at 10:19 PM, Shijun Sun shij...@microsoft.com wrote:
It'd be very helpful if PushRegistration can have a read-only attribute for
ExpirationTime or something like that. Webapps can be more proactive if the
On 22 October 2014 22:19, Shijun Sun shij...@microsoft.com wrote:
Thanks Martin. It'd be very helpful if PushRegistration can have a read-only
attribute for ExpirationTime or something like that. Webapps can be more
proactive if the ExpirationTime is set.
I was thinking that this was a
On Wednesday, October 22, 2014 8:41 AM. John Mellor wrote:
See https://github.com/w3c/push-api/issues/74 and
https://github.com/w3c/push-api/issues/82 for more details on when and why
registrations might expire in a typical push service.
Thanks John for the pointers!
I have a few more
On Wednesday, October 22, 2014 9:33 PM, Martin Thomson wrote:
A UA needs to be made aware of expiration or invalidation. This can be one
of two ways: an explicit, prior commitment to a definite expiration, or -
because I've been told that time-based expiration has issues - an explicit
Folks,
I'm looking for help to a couple more questions on the Push API.
1. What is the typical lifetime expected for a PushRegistration?
2. IF a PushRegistration can expire, what would be the right option(s) to
renew the push service?
All the Best, Shijun
