Andrea Giammarchi

let me simplify my question: are you expecting to use **just** a *Shared Worker* instead of a *Worker* from any tab main? 'cause *that* is a bit of a stretch...

and then again ... I see *SharedWorker* is **not available in workes** ... now that's a bummer: https://webreflection.github.io/is-it-worker/?SharedWorker

> Perhaps, however, the limitation you're seeing is due to how Coincident works? this link simply asks a worker to tell if something is available on its global scope and...

P.S. I don't read *Available in Workers* in this page anywhere: https://developer.mozilla.org/en-US/docs/Web/API/SharedWorker

> for the sake of browser and backend server cpu and memory resources, as well as bandwidth usage - to have them all share a single, consistent source well ......

> The SharedWorker interface represents a specific kind of worker that can be accessed from several browsing contexts, such as several windows, iframes or even workers that deserves an issue...

> It is all a very common use case of sharedworkers, and even mentioned in that same mdn doc. And many other places. sure, but if I can't create a...

just FYI that (my) page doesn't lie ... https://stackoverflow.com/a/30831231

if current state is confirmed (no SharedWorker on Workers ... and I think it is) I need to think upside-down the dance ... or test Atomics would work from a...

uhm ... the thing is, you never need more than a Worker per page/tab *but* you also could: * reuse the same WebSocket created in *main*, `coincident/server` uses main to...