W3C home > Mailing lists > Public > public-geolocation@w3.org > September 2014

Re: Geofencing alternative proposal

From: Michael van Ouwerkerk <mvanouwerkerk@google.com>
Date: Tue, 23 Sep 2014 11:31:03 +0100
Message-ID: <CAF40kP6C8rhOfD9DuH1Y2wPMoDgF3OLdSfbsRYG3CgSATB7+TA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: John Mellor <johnme@google.com>, Marijn Kruisselbrink <mek@google.com>, Alex Russell <slightlyoff@google.com>, "public-geolocation@w3.org" <public-geolocation@w3.org>
Martin, I think it means that before functional events (e.g. fetch, push)
start firing, activate is fired once. Not once before each fetch event.
Does that sound right?

/m


On Tue, Sep 23, 2014 at 11:25 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 22 September 2014 03:22, John Mellor <johnme@google.com> wrote:
> > No, activation also only happens once (see SW lifecycle definition).
>
> This seems to suggest otherwise:
>
> """
> onactivate:
> After successful installation and just prior to receiving functional
> events (e.g., fetch), the activate event is dispatched.
> """
>
> I haven't had a lot of sleep, but this seems very clear to me.  Maybe
> there is some way to interpret this to mean that activate is not fired
> just prior to functional events, but I can't work it out.  The note
> would seem to reinforce my interpretation:
>
> """
> Note: Like install event, this event may extend its lifetime using
> event.waitUntil(), however developers should note that activation is
> particularly performance sensitive. Performance sensitive events may
> be queued and will be delayed until successful completion of
> onactivate.
> """
>
>
Received on Tuesday, 23 September 2014 10:31:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:51:09 UTC