Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Socket.IO
Home
+ new post
About this group
Join this group
Message from discussion socket.io or sockJS
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Guillermo Rauch  
View profile  
 More options Apr 28 2012, 10:14 am
From: Guillermo Rauch <rau...@gmail.com>
Date: Sat, 28 Apr 2012 11:14:42 -0300
Local: Sat, Apr 28 2012 10:14 am
Subject: Re: socket.io or sockJS
Print | View thread | Show original | Report this message | Find messages by this author

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.

On Sat, Apr 28, 2012 at 10:04 AM, StigFærch <s...@8620.dk> wrote:
> 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.

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

--
Guillermo Rauch
LearnBoost CTO
http://devthought.com

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google