Very cool! Excited to see what comes next.

Is there anything people looking forward to these features should know to plan? Like, I was about to start doing some load balancing stuff soon. Is that a waste of my time and I should just work on the core logic and figure load balancing is just going to be made easier in the near future and I shouldn't waste my time with it? Or should I roll my own option for now and then just figure at some point I should be able to transition to something that performs better in the future?

Will there be 'websocket.io-client', high-performance server-side WebSockets client module, in the near future?

I noticed `websocket.io` is depends on a module called `easy-websocket` which is registered with NPM with description "lain and simple websocket client" but no where to be found on Github. Is `websocket.io` what we are supposed to be using as client?

I've been using websocket.io and I must say, refactoring the websocket server code out of socket.io was a great decision. There isn't really any clean, low-level websocket implementations for node that worked anymore after recent versions of Chrome and Firefox. Websocket.io is really clean, small, and works in all browsers.

Socket.io has a lot of bloat that isn't required if all you need is a simple Websocket communications. Please do not add long-polling to websocket.io, it's the wrong place to do that type of abstraction.

Brilliant - didn't know websocket.io had been broken out. I was patiently waiting for @miksago to update https://github.com/miksago/node-websocket-server however it had become clear this was a very low priority for him (fair enough).

> There isn't really any clean, low-level websocket implementations for node that worked anymore after recent versions of Chrome and Firefox.

Not true. I continue to use https://github.com/Worlize/WebSocket-Node with great success.