Re: [ServiceWorker] Workers & SharedWorkers within ServiceWorkers (#678)

I am curious about the possible next steps for this issue, to allow service workers to talk to shared workers, and for a service worker to count as a reference count for keeping a shared worker alive.

Is it getting an update to the [Shared worker part in the whatwg document](https://html.spec.whatwg.org/multipage/workers.html#sharedworker), then a corresponding service worker spec change? Although looks like event.waitUntil already exists in the service worker spec, maybe that is enough? Or is it more important to have an implementation try it out first?

If it is about the whatwg document, in section 10.2.6.4:

Step 7 mentions:

    Let docs be the list of relevant Document objects to add given the incumbent settings object.

Seems like `docs` might want to be expanded to some term that encapsulates Document or Service Worker objects, something like `owners`, but maybe not that exact word. Maybe there is already a spec term for this: "thing that holds a reference to target and if thing goes away and target has no other things with references, target goes away"?

Then these steps adjusted to use those terms:

Step 8.7.7:

    Add to worker global scope's list of the worker's Documents the Document objects in docs.

And Step 11:

    Add to worker global scope's list of the worker's Documents the Document objects in docs.

If a whatwg doc update is the next step, and if it helps, I can start a thread on the whatwg list about it. If an implementation is best, then I can file a bug for Gecko to track experimenting with it.


---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/678#issuecomment-106559240