On Fri, May 20, 2016 at 8:04 AM, Ben Kelly <[email protected]> wrote: > On Fri, May 20, 2016 at 10:56 AM, Boris Zbarsky <[email protected]> wrote: > >> Thoughts? Any obvious problems with this plan? > > We have the concept of network requests made from workers not associated > with a single document. For example, SharedWorker attached to multiple > documents or a ServiceWorker servicing a push event. In theory we want the > same load grouping behavior to abort requests if those workers terminate, > etc. > > If we are refactoring things, can we include that concept as well?
I *think* the current setup that we have dedicated workers is that each worker gets its own loadgroup, and that all XHR/fetch()/importScripts() loads are added to that loadgroup. Ideally that loadgroup should be added as a child loadgroup of the owning document, or the owning worker. But I'm not sure that is the case. For SharedWorkers/ServiceWorkers, we should just skip the last step. I.e. we should not make the loadgroup be a child of any other loadgroup. Is that not what we're currently doing? / Jonas _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
