W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2014

Re: Push API - PushRegistration and lifetime

From: John Mellor <johnme@google.com>
Date: Wed, 22 Oct 2014 16:40:32 +0100
Message-ID: <CAG_kaUa57hz-8-KNhNHaaS12GDTJu=4R=ScGLtzwj6tmpdtu6Q@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Shijun Sun <shijuns@microsoft.com>, public-webapps <public-webapps@w3.org>
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.

On 22 October 2014 16:33, Martin Thomson <martin.thomson@gmail.com> wrote:

> On 21 October 2014 12:14, Shijun Sun <shijuns@microsoft.com> wrote:
> > 1. What is the typical lifetime expected for a PushRegistration?
>
> mu.  There's only the expectation that the registration is useful.
>
> > 2. IF a PushRegistration can expire, what would be the right option(s)
> to "renew" the push service?
>
> They certainly can expire, but the idea is that you would receive some
> notification (currently badly named `pushregistrationlost`) when that
> happens.
>
>
Received on Wednesday, 22 October 2014 15:41:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:32 UTC