Re: [w3c/ServiceWorker] Introduce a parallel queue for running Jobs (#1229)

jakearchibald requested changes on this pull request.

This is a good step, but eventually I'd like to replace the whole "job" concept with a parallel queue.

> @@ -257,6 +257,14 @@ spec: webappsec-referrer-policy; urlPrefix: https://w3c.github.io/webappsec-refe
         Note: A user agent may use a separate task source for each functional event type in order to avoid a head-of-line blocking phenomenon for certain functional events.
   </section>
 
+  <section>
+    <h3 id="user-agent-bootup">User Agent Boot up</h3>
+
+    A user agent has an associated <dfn export id="dfn-service-worker-manager">service worker manager</dfn>.
+
+    A user agent *must* [=start a new parallel queue=] when it boots up and set the [=service worker manager=] to the result value.

Does this need to be scoped to the whole user agent, or is per-origin enough?

>  
               Note: For a register job and an update job, the user agent delays queuing a task for running the job until after a {{Document/DOMContentLoaded}} event has been dispatched to the document that initiated the job.
 
-          1. Else if |job|'s [=job type=] is *unregister*, run [=Unregister=] with |job| [=in parallel=].
+          1. Else if |job|'s [=job type=] is *unregister*, run [=Unregister=] with |job|.

This is a good step. Eventually I'd like to get rid of the "job" concept entirely, and replace it with appending steps to the appropriate parallel queue.

-- 
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/pull/1229#pullrequestreview-77789614