How does JavaScript handle WebSocket timeout

This article is about how JavaScript handles WebSocket timeouts. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Processing WebSocket timeout

Usually, after a WebSocket connection is created, if you are not active, the server will disconnect (time out) your connection after 30 seconds. The firewall will also be disconnected after a period of inactivity.

To prevent timeout problems, you may need to intermittently send empty messages to the server. To do this, you can add the following two functions to your code: one to maintain the connection and the other to cancel the retention of the connection. With this technique, you can control the timeout problem.

Use a timerID:

Var timerID = 0 function keepAlive () {var timeout = 15000; if (webSocket.readyState = = webSocket.OPEN) {webSocket.send ('');} timerId = setTimeout (keepAlive, timeout);} function cancelKeepAlive () {if (timerId) {cancelTimeout (timerId);}}

The keepAlive () method should be added at the end of the onOpen () method of the webSOcket connection, while cancelKeepAlive () should be added at the end of the onClose () method.

Thank you for reading! This is the end of the article on "how JavaScript handles WebSocket timeouts". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!