3 ms·
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-lev
by wavephorm 15y ago
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.
- moderation 15y agoBrilliant - didn't know websocket.io had been broken out. I was patiently waiting for @miksago to update https://github.com/miksago/node-websocket-server https://github.com/miksago/node-websocket-server however it had become clear this was a very low priority for him (fair enough).
- maratd 15y ago> 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 https://github.com/Worlize/WebSocket-Node with great success.