- From: aliams <notifications@github.com>
- Date: Wed, 24 Aug 2016 15:12:53 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Wednesday, 24 August 2016 22:13:42 UTC
Thank you for your very detailed analysis @wanderview! There are two main points from your summary that I'd like to pull out as arguments _for_ allowing multiple service worker instances: > thread pool does help with the "blocking worker" case ...and... > it does seem desirable to allow service worker thread instances to run co-located in the same process as the controlled window I think the real key here is to **remove the restriction of only allowing one service worker instance that handles all events**. By removing this restriction we should be able to optimize for the two scenarios above as well as allowing push and background sync events that can be handled in a timely and concurrent fashion in the background. -- 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/756#issuecomment-242224840
Received on Wednesday, 24 August 2016 22:13:42 UTC