Re: [slightlyoff/ServiceWorker] Enabling multiple Service Workers for a single scope (#921)

I also think there are lots of unknowns that would have to be solved at the cost of increased complexity:

1. What does updating a "second service worker" for the same scope look like?  Can the primary service worker still be processing events while this happens?  Or is it essentially treated as a single new service worker effectively?  Running in the same thread implies a single new service worker.
2. How would the separate service worker instances be exposed?  Would registration.active by an array of ServiceWorker objects?  How would the page know which one to postMessage() to?

I'm not saying that we should never do this, but I think its still pretty early days in terms of developers figuring out which patterns they want and need.  My gut feeling is we should wait to see if a dominant design emerges in the framework ecosystem before baking something into the platform itself.

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