Blink side of requestSyncEvents() function.

Source/modules/serviceworkers/ServiceWorkerGlobalScope.idl

 /*
  * Copyright (C) 2013 Google Inc. All rights reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions are
  * met:
  *
  *     * Redistributions of source code must retain the above copyright
  * notice, this list of conditions and the following disclaimer.
  *     * Redistributions in binary form must reproduce the above
@@ skipping 18 matching lines @@
  */
 [
     GlobalContext=ServiceWorkerGlobalScope,
     RuntimeEnabled=ServiceWorker,
 ] interface ServiceWorkerGlobalScope : WorkerGlobalScope {
   attribute EventHandler onactivate;
   attribute EventHandler onfetch;
   attribute EventHandler oninstall;
   attribute EventHandler onmessage;
   attribute EventHandler onsync;
+  [CallWith=ExecutionContext] void requestSyncEvents(optional boolean requested, optional Dictionary options);

[michaeln, 2014/04/03 22:29:27]

The onsync event seems pretty solid but the registration/request mechanism is
less clear? Assuming we get a number of possible optional events, do we want
individual IDL to toggle each on/off or is there a generalized mechanism?

Until thats more clear, I wonder if we want to automatically toggle on/off based
on EventTarget::hasEventListeners('sync') at the end of script parse/eval?

I'm considering doing something like that for onfetch since we have some early
customers that don't care about that event either.

[jkarlin, 2014/04/04 12:05:29]

Sync needs to toggle on and off its event listener dynamically (to avoid waking
up a SW needlessly).  It also needs to be able to provide hints as to when it
wants the sync event to hire.  The toggling and the hints could be two separate
functions, or they could be one.  I had intended  to place both within the
requestSyncEvents function.


On 2014/04/03 22:29:27, michaeln wrote:

 };