last version is unstable

[Gorokhov]

when transports are configured like [ws, flashsocket,htmlfile,xhr....] chrome(14.0.835.163 m) on win7 doesn't cacth flashsocket falls back to xhr-polling, the connection is terribly long and after couple of seconds it looses connection. when ws disabled chrome connects faster and even works for a while, but on linux(ubuntu 11.04, chrome 13.0.782.220) page never loads if i click stop button i stop receiving new messages. in case i restart server (not sure about this but looks like the same behaviour is if internet connection is lost for a while) when trying to reconnect, it never works correctly, and get a js error

keep getting log: (node) Hit max file limit. Increase "ulimit - n"
finally node crashes

and i remind you about antivirus probs, and some clients even not using antivirus keep getting errors and disconnects

this is terrible it's completly not usable , i had to revert it from production.

[databyte]

After disabling websockets, I too noticed that Chrome 14 skips over flashsocket and uses xhr-polling. I don't have issues with memory limits or losing connection afaik since we've only been in production with websockets off for a couple days (on the weekend where we don't get much traffic).

So +1 on why Chrome 14 skips over flashsocket.

[3rd-Eden]

Flashsocket is a fallback / polyfill for WebSockets, so if native Websockets are detected it's not loaded.

As for @Gorokhov you probably want to increase in your ulimit -n to increase file descriptors then, it's not something that socket.io can do for you.