Re: [w3c/ServiceWorker] Run Job does not specify which event loop to queue its tasks on (#1224)

What is the current status of https://github.com/w3c/ServiceWorker/pull/1229 ? 

The `Run Job` algorithm also confused me (today) with it's use of task queuing, followed by immediately running the actual job "in parallel". 

I agree the parallel queue appears like the right primitive to express what a "job queue" is. There are parallels(no pun intended) with the [shared-worker-manager](https://html.spec.whatwg.org/multipage/#shared-worker-manager) used in the HTML spec(which have been noted in the PR already I see). 

Reading up on the comments above, I think the use of a parallel queue already implies a kind of "event-loop" running those steps serially, hence there would be no need to define a new type of event-loop(the open PR doesn't seem to attempt doing that either). 

Finally, perhaps we could also get rid of the [scope-to-job-queue-map](https://w3c.github.io/ServiceWorker/#dfn-scope-to-job-queue-map)? It would seem like scoping the job queue per scope-url would not offer material benefit at the spec level, just like scoping it per origin doesn't, as a un-scoped wording still leaves the possibility for the UA to run multiple job queues in parallel per origin or even scope, I think(the parallelism would not be observable). 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1224#issuecomment-613557860