How JavaScript handles the timeout of WebSocket

Editor to share with you how JavaScript deals with WebSocket timeouts, I believe most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

Processing WebSocket timeout

In general, after the WebSocket connection is created, if there is no activity within 30 seconds, the server will time out the connection, and the firewall can time out the connection with no activity per unit cycle.

To prevent this from happening, you can send an empty message to the server at regular intervals. You can implement this requirement through the following two functions, one to keep the connection active and the other specifically to end this state.

Add a timerID

Var timerID = 0 function keepAlive () {var timeout = 15000; if (webSocket.readyState = = webSocket.OPEN) {webSocket.send ('');} timerId = setTimeout (keepAlive, timeout);} / / Welcome to join the front-end full-stack development exchange circle: 1007317281function cancelKeepAlive () {if (timerId) {cancelTimeout (timerId);}}

The keepAlive () function can be placed at the end of the onOpen () method of the WebSocket connection, and cancelKeepAlive () at the end of the onClose () method.

The above is all the contents of the article "how JavaScript handles WebSocket timeouts". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!