Socket.io delay in firing the “disconnect” event?

Question

I have a socket.io client connected to a node.js server. If I kill node.js at the command line, the client immediately freezes (i.e., communication stops), but there is a ~2

Answer 1

I think this is likely a design pattern. The client may be presuming the server is 'temporarily' unreachable (network trafic etc) and essentially will keep trying to reach it... until the client timeout kicks in.

I send a disconnect (socket.disconnect()) to the server directly from the client, and I don't get this issue.

Answer 2

Yes. close timeout .