WebSockets - rebuild base-webapp as SPA?

[jackyscript]

After the current displayed page is refreshed or changed by using the navigation bar, an established WebSocket connection is destroyed and created again.

The goal of this issue is to find the answers to the following questions:

1. WebSocket best practices, what should be the expected life cycle of a connection?
2. Assuming an already established connection should be maintained at all cost, should practices be considered to ensure this behaviour, e. g. implementing base-webapp as an SPA?
3. How does the current approach compare to using technologies like Server Sent Events or SharedWorker? Would those be an addition to the current portfolio or do they even represent a better alternative?

[jackyscript]

Further references addressing this issue:

• How keep a Websocket connection persistent, even after page refresh?
• Keep WebSocket connection alive after refresh
• How to maintain a WebSockets connection between pages?
• Node.js and Websockets best practices checklist | Voodoo Engineering
• Reconnecting a WebSocket without creating a new instance
• Websockets. Loss of internet, keep-alive messages, app architecture etc
• When working with websockets should I open a new websocket connection for every different task? Or should I do everything within one connection?