Re: [w3c/ServiceWorker] Missing task queuing (#1403)

The way I read it the original thread is just waiting around when we reach step 4, until that reaches step 4.13. So there is nothing to schedule, since the thread is just waiting.

But I do agree that this does seem unclear. Also "Run Service Worker" isn't consistently used the same way. Definitely for the cases where Run Service Worker is invoked synchronously from idl methods, as for example in post message, blocking the calling thread until the worker script has been evaluated doesn't make sense, so at least for those cases (ones where no callback steps are passed in to run service worker) my interpretation doesn't make sense.

And since afaict callback steps actually only seemed to be used in one place (in the Update algorithm), some kind of scheduling probably makes sense. But I'm not sure what task queue tasks would get posted to. It's not like the "update" algorithm is running on any particular task queue (actually I have no idea where the "Run Job" algorithm is posting tasks to. All these tasks really aren't associated with any particular agent, but afaict event loops are always associated to agents?

-- 
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/1403#issuecomment-489160695