4 ms·
Sounds like a service worker, for which there's only one active at a time for all tabs (and can communicate with them) could help with your client side issues.
by qwtel 5y ago
Sounds like a service worker, for which there's only one active at a time for all tabs (and can communicate with them) could help with your client side issues.
- greeklish 5y agoHere's an article on how to multiplex websockets [1] It looks pretty clever, I wish more websocket frameworks like [2] supported this out of the box (with failovers for safari). [1] https://dev.to/ayushgp/scaling-websocket-connections-using-shared-workers-14mj https://dev.to/ayushgp/scaling-websocket-connections-using-s... [2] https://www.npmjs.com/package/hydrated-ws https://www.npmjs.com/package/hydrated-ws
- taf2 5y agoThis works great just not for safari since for some reason the WebKit team felt in 2015 it made since to remove SharedWorkers https://stackoverflow.com/questions/28310501/why-did-safari-drop-support-for-sharedworker https://stackoverflow.com/questions/28310501/why-did-safari-...
- infomax 5y agoFrom the link you shared it looks like they are restoring the functionality: https://bugs.webkit.org/show_bug.cgi?id=230382 https://bugs.webkit.org/show_bug.cgi?id=230382