[Webkit-unassigned] [Bug 149850] Reinstate support for SharedWorkers

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=149850

--- Comment #15 from Stu Kabakoff <sakabako at gmail.com> ---
(In reply to Maciej Stachowiak from comment #11)
> Recent commenters who are interested in shared workers, can you please share
> the following info:
> 
> - Are there any existing websites or apps you can maktion that would use
> SharedWorkers if they were brought back, or which currently use
> SharedWorkers in other browsers?
> 
> - Can you tell us more about how you'd like to use SharedWorkers? 
> 
> (I recognize some have already commented with a bit more detail; I don't
> totally get what is meant by "local database" though. Is it using IndexedDB?
> If yes, why is a shared worker needed? If no, how is it ultimately storing
> things?)

The use cases that I hit fall into one of two categories: networking and data.

- Having a multi-window app with a single WebSocket/WebRTC connection to a server. This is my use case for a real time application.
- Using a wasm database that saves to either IndexedDB or appcache. This library is an example and specifically calls out Safari: https://github.com/wireapp/websql
- An in memory database, in my case we're using LokiDB to react to changes provided by a shared worker holding the socket.
- Synchronizing data in multi-window apps with a single source of truth.

To anyone reading this, we have been able to work around this using leader election from this library: https://github.com/pubkey/broadcast-channel

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200615/105a6540/attachment.htm>