Wednesday, 15 January 2014

node.js - Is it safe to set a high close timeout on socket.io? -



node.js - Is it safe to set a high close timeout on socket.io? -

i have web application user needs connected. default, socket.io disconnect connection after 60 seconds. have 'reconnection' turned on though, closing , reopening connection every minute. can cause issues feeds/notifications connected clients. safe set timeout lets say, 10 minutes, or perchance higher? there reason low right now?

my guess may misinterpreting 'close timeout' configuration. not cause connection closed after 60 seconds. (heartbeats pointless if clients reconnected).

if client disconnects, close timeout amount of time server wait before releasing resources associated connection. essentially, allows clients intermittent connectivity issues effort reconnect before server has forgotten them. setting close timeout 10 minutes bad thought since tie server resources.

if clients are, in fact, disconnecting every 60 seconds, then, samjm said, else wrong.

node.js timeout socket.io

No comments:

Post a Comment