In Intern 4.x and 5-pre, the websocket channel between a remote and the server may close unexpectedly if no communication occurs for an extended period of time. For example, if a client takes a couple minutes to download a very large test set, during which time no messages will be sent over the websocket, the browser may kill the connection.
The WebSocket channel should send periodic ping messages to keep the channel alive. We should also try to reopen unexpectedly closed sockets.
In Intern 4.x and 5-pre, the websocket channel between a remote and the server may close unexpectedly if no communication occurs for an extended period of time. For example, if a client takes a couple minutes to download a very large test set, during which time no messages will be sent over the websocket, the browser may kill the connection.
The WebSocket channel should send periodic ping messages to keep the channel alive. We should also try to reopen unexpectedly closed sockets.