Mobile browsers throttle client-side JavaScript and web socket connections

[goloroden]

What is this bug about?

Seems like mobile browser throttle client side JS which causes Websocket Connections to freeze while being inactive.

What steps are needed to reproduce the bug?

• Write a simple WS server and client
• Load the client in a mobile browser and wait
• Try to send a command after activating the tab again
• See if the client throws an error due to inactive Websocket connection
• Repeat the same process but keep sending heartbeats from the server in the background to keep the connection alive

What is the expected result?

• It should be possible to send commands after being inactive

What is the actual result?

• The client throws an error that the connection might be

What else should we know?

• Safari dropping web socket connection due to inactivity when page not in focus socketio/socket.io#2924
• Reverse the direction of ping/pong messages primus/primus#534
• https://news.ycombinator.com/item?id=13471543

[goloroden]

Now that we have decided to drop support for WebSockets (see #129) we need to re-check whether this problem still exists for the Streams API.

[goloroden]

We don’t use web sockets any longer, so closed.