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

> As far as I can tell, this proposal seems to be based on the belief that it's easier for sites/optimization services to drop in a new \<script\> tag to register a second service worker, than it is for those same sites/optimization services to drop in a new importScripts() call to work within the existing service worker?

That's part of the motivation, but a bigger part is the desire to have the code in the two service workers be more independent of each other.

As an example, let's say you have a service worker module that does some alternative compression/content-encoding, and you have another service worker module that does caching or offline availability. Currently, these two things need to be combined in the same fetch handler. This is a use case for having layered fetch handlers.

---
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-229685843