Issues keeping linode sockets open: nodeJS+socketIO and ssh
Anyway there are reports of connection cycling when trying to deploy this set of software on Linode. See
I've notice this disconnect/reconnect cycling doesn't happen when the server and clients are deployed on an isolated home network – but I am seeing that cycling when hosted on Linode. So it is either network or Linode related.
I recall a similar issue with ssh sessions to Linodes hanging/disconnecting, see
Is there any reason to think these issues are related, and have a common solution? If so, what might that solution be?
6 Replies
i was debating whether to go linode or ec2. problematic websocket support is a no go
@DrPaulBrewer:
I recall a similar issue with ssh sessions to Linodes hanging/disconnecting, see
http://forum.linode.com/archive/o_t/t_4 … _open.html">http://forum.linode.com/archive/ot/t4793/keepingansshsessiontomylinode_open.html Is there any reason to think these issues are related, and have a common solution? If so, what might that solution be?
Unless I'm mistaken, that one was caused by the user having incorrectly configured their SSH software…
I have come to the following quick conclusions:
1. socket.io may be a bit early in the technology cycle…. There are all sorts of problems deploying anything important on socket.io; others, e.g. on stackoverflow, have had various problems with corporate firewalls and other issues.
2. Problems I've seen can be duplicated at other sites I have access to… so the connection cycling is not a LINODE or a VPS issue.
3. JSON RPC polling is good enough for me… don't really need to support websocket for what I'm working on… nodejs is still useful in this environment, and I really like nodejs programming model that can simplify coding -- and not worrying about database locking and multiple moving parts, etc…