Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Controlling the heartbeat timeout from the client in socket.io

I have mobile clients connected to a node.js server, running socket.io via xhr-polling. I have two type of clients:

  • Type A

    When the connection breaks up due to network problems (or that the client crashes) the default heart beat timeout is too long

  • Type B

    When the connection breaks up for this client I need to give it more time to recover - it is more important that the client recovers than the server breaks the connection/session

So my question is how to I configure (if it is possible) the heartbeat timeouts from the actual client?

like image 448
Martin Avatar asked Oct 10 '12 08:10

Martin


People also ask

Does socket.io have a timeout?

So, you can configure both the server and client side timeout settings by setting the following timeout properties on the engine.io component inside of socket.io.

What is a heartbeat timeout?

The heartbeat timeout value defines after what period of time the peer TCP connection should be considered unreachable (down) by RabbitMQ and client libraries. This value is negotiated between the client and RabbitMQ server at the time of connection. The client must be configured to request heartbeats.

Does socket.io use long-polling?

First, Socket.IO creates a long-polling connection using xhr-polling. Then, once this is established, it upgrades to the best connection method available. In most cases, this will result in a WebSocket connection.

Does socket.io reconnect automatically?

In the first case, the Socket will automatically try to reconnect, after a given delay.


1 Answers

As far as I can tell, there are 2 values that matter here: the server sends heartbeats to the client every heartbeat interval seconds; the client responds directly, if there is no response, the server decides the client is dead. The client waits for a heartbeat from the server for heartbeat timeout seconds since the last heartbeat (which should obviously be higher than the heartbeat interval). If it hasn't received word from the server in heartbeat timeout seconds, it assumes the server is dead (and will start disconnecting / reconnecting based on the other options you have set.

Default values are heartbeat interval = 25s and heartbeat timeout = 60s. Both items are set on the server, the heartbeat timeout is sent to the client upon connecting.

Changing the heartbeat timeout for a single client is easy:

var socket = io.connect(url); socket.heartbeatTimeout = 20000; // reconnect if not received heartbeat for 20 seconds 

However on the server, the heartbeat interval value seems to be part of a shared object (the Manager, which is what you get back from your var io = require("socket.io").listen(server) call), which means that it can't easily be changed for individual sockets.

I'm sure that with some socket.io hacking you should be able to make it happen, but you might break other stuff in the process...

like image 135
Claude Avatar answered Oct 17 '22 10:10

Claude