socket.io or sockJS
198 views
Skip to first unread message
StigFærch
Apr 28, 2012, 9:04:23 AM4/28/12
to sock...@googlegroups.com
I'm in the process of choosing different components for a node.js
project.
Currently I'm trying to find out whether to use socket.io or sockJS.
project.
Currently I'm trying to find out whether to use socket.io or sockJS.
It's important to me that it scales good, as I hope that my project
eventually will grow big. Does socket.io scale just as well as sockJS - what are the differences at this
point?
I know that sockJS is concentrating on the transport layer and not
getting bloated with others stuff. What is your take on this?
If a key person in socket.io gets hit by a bus (God forbid), will socket.io die?
Any other things worth mentioning comparing the two?
eventually will grow big. Does socket.io scale just as well as sockJS - what are the differences at this
point?
I know that sockJS is concentrating on the transport layer and not
getting bloated with others stuff. What is your take on this?
If a key person in socket.io gets hit by a bus (God forbid), will socket.io die?
Any other things worth mentioning comparing the two?
Guillermo Rauch
Apr 28, 2012, 10:14:42 AM4/28/12
to sock...@googlegroups.com
The equivalent to sockjs is http://github.com/learnboost/engine.io, not socket.io. Socket.IO does a lot more. As far as scalability, both require sticky load balancing.
The main difference between sockjs and engine is that the latter performs an upgrade from long polling to websocket. It thus guarantees the highest possible reliability in any network or device, and the fastest connections. It doesn't need "fallbacks". It therefore makes Flash also a really good option, because Flash slowness to connect and policy timeouts don't matter. Please check out the Engine.IO README for a more detailed explanation.
Reply all
Reply to author
Forward
0 new messages