Re: [w3c/ServiceWorker] allow service workers to created nested dedicated workers (#1529)

You make a good point about the lifetime - a Dedicated Worker spawned by a Service Worker probably should be tied to the SW's lifetime, which I understand to be somewhat unpredictable/ephemeral... 

At least as far as my use case goes for this, I think that if Android Chromium could ever get around to adding [support for Shared Workers](https://issues.chromium.org/issues/40290702), then many issues like this would be largely irrelevant. I, and many others, are doing a lot of convoluted dances between different workers/threads, with leader election and various ways to message between them, all because Shared Workers are not a viable option when missing on 50% of web visitors. 

If we had shared workers, instead of a SW needing to spawn a dedicated (or shared) worker, it could just pass messages to one that was already created by one of the main threads (which might not even be active anymore.

Shared Workers really are the holy grail of all of this - the rest is largely just terrible "polyfill" kludges. 

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

Message ID: <w3c/ServiceWorker/issues/1529/2643921948@github.com>