- From: Jungkee Song <notifications@github.com>
- Date: Tue, 21 Nov 2017 02:54:42 +0000 (UTC)
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 21 November 2017 02:55:10 UTC
jungkees commented on this pull request. > 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|. That'd mean the implementations should create and maintain a separate thread for each scope. That may be an ideal design which allows parallel register/update/unregister even, but a single (off-the-main) thread executing the jobs from all the job queues is what we currently have. I also would like to hear what implementers think on this. -- 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#discussion_r152168068
Received on Tuesday, 21 November 2017 02:55:10 UTC