NodeJS is a new asynchronous server-side javascript engine that can act as a webserver. socket.io is a module for nodejs that serves as an abstraction library on the server, and also serves clients, providing a virtual socket between the server and the client (which might be an actual websocket in HTML 5, or something else depending on the browser).

Anyway there are reports of connection cycling when trying to deploy this set of software on Linode. See https://github.com/LearnBoost/Socket.IO-node/issues/224

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
archive/o_t/t_4793/keeping_an_ssh_session_to_my_linode_open.html

Is there any reason to think these issues are related, and have a common solution? If so, what might that solution be?

A packet capture using tcpdump on both ends might reveal something. Also, if you have a NAT on your local end, trying to test without that might be helpful.

_________________

/* TODO: need to add signature to posts */

Oh I sincerely hope it's not a Linode issue! I'm just about to build a Node.js+Socket.io powered app!

+1.
i was debating whether to go linode or ec2. problematic websocket support is a no go

I seriously, seriously doubt this has anything to do with Linode.

-Chris

Unless I'm mistaken, that one was caused by the user having incorrectly configured their SSH software...

A quick "thank you" to everyone who replied.

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...