SharedWorker use cases

[jagadeeshaby]

I have 2 top level sites www.site11.com and www.site22.com and both of them embeds www.connect11.com website which spins up a new shared worker called "Connect11SharedWorker" which does take care of keeping "master tab" information and make sure only one tab handles audio at any time.

What i have observed is when i navigate to site11.com , there is one shared worker called Connect11SharedWorker spun up and site22.com there is another shared worker with the same name "Connect11SharedWorker" is spun up too, this is problematic because there are 2 shared worker which are trying to identify the master tab and trying to handle audio.

My questions here are

• how do we prevent spinning up same shared worker multiple times per top level sites which basically takes away the meaning of true shared worker concept
• could we use FPS to prevent such duplicate shared workers getting spun up?
• Is there a alternative for shared worker to read data from shared storage?
• When is storage partition getting rolled out?

[jagadeeshaby]

Following up on this. I see that it's getting launched as part of - https://groups.google.com/u/0/a/chromium.org/g/blink-dev/c/24hK6DKJnqY/m/aHSXjm01AgAJ. shall we get more updates on the support for shared worker as part of storage access API?

My customer use cases will get seriously impacted by this issue as we use shared worker for web RTC signalling and web socket management.

[johannhof]

Hi @jagadeeshaby, you can participate in the deprecation trial, see https://developer.chrome.com/blog/storage-partitioning-deprecation-trial/

[johannhof]

We're still discussing the details of storage support for SAA in privacycg/storage-access#102, which you can follow for updates :)