On Thu, Jul 16, 2015 at 12:50 AM, Jonathan Kingston <jonathan@jooped.com> wrote: > It's not immediately clear how the browser would handle safely letting the > client side control the timing of the clear. > Consider the case of a new, background-requested Service Worker script that is asynchronously installing. Perhaps it wants to delay this sort of thing until it knows it's back online. > However I can see syncing of user data that is important to the > application(for example user created documents in offline mode) and > unrelated to perhaps user credentials something a developer would wish to > control somewhat. > > On Wed, 15 Jul 2015 at 20:11 Mike West <mkwst@google.com> wrote: > >> Do you want to control timing? When would you want to do this on >> something other than a response? Sorry, the use case just isn't clear to >> me. >> >> -mike >> >> -- >> Mike West <mkwst@google.com>, @mikewest >> >> Google Germany GmbH, Dienerstrasse 12, 80331 München, >> Germany, Registergericht und -nummer: Hamburg, HRB 86891, Sitz der >> Gesellschaft: Hamburg, Geschäftsführer: Graham Law, Christine Elizabeth >> Flores >> (Sorry; I'm legally required to add this exciting detail to emails. Bleh.) >> >> On Wed, Jul 15, 2015 at 2:03 PM, Alex Russell <slightlyoff@google.com> >> wrote: >> >>> If you want to control timing, an API to do this would be useful. >>> >>> On Wed, Jul 15, 2015 at 10:20 AM, Mike West <mkwst@google.com> wrote: >>> >>>> On Wed, Jul 15, 2015 at 10:11 AM, Alex Russell <slightlyoff@google.com> >>>> wrote: >>>> >>>>> This looks great! In particular, the sandboxing looks like absolutely >>>>> the right thing. >>>>> >>>>> I didn't see anything in the draft about an API for this capability. >>>>> Have we thought about adding one? >>>>> >>>> >>>> Is it necessary? Happy to add something if there's clarity around use >>>> cases that we can't otherwise serve. >>>> >>>> -mike >>>> >>> >>> >>
Received on Thursday, 16 July 2015 08:12:24 UTC