Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SockJS Support #113

Open
johnjelinek opened this issue Apr 26, 2014 · 4 comments
Open

SockJS Support #113

johnjelinek opened this issue Apr 26, 2014 · 4 comments

Comments

@johnjelinek
Copy link

Can we migrate to SockJS instead of Socket.io?

@pilwon
Copy link
Owner

pilwon commented May 3, 2014

@johnjelinek This looks like a fantastic replacement.

@yaru22 What do you think about SockJS?

@yaru22
Copy link
Collaborator

yaru22 commented May 4, 2014

Just some thoughts here...

I've seen a few people saying not to use socket.io 0.9 as it doesn't scale horizontally and susceptible for DDoS attack and I'll take their advice. However, socket.io seems to be in active development for 1.0 release and so is engine.io (communication layer for socket.io but you can use it without socket.io).

Looking at lib/ directory in SockJS, it seems like most of the code hasn't been updated in a while. Maybe it means the library is quite stable?

The approach I would suggest is using primus with SockJS or engine.io or whatever primus supports. This way, we can easily switch among SockJS, engine.io, etc.

Read this just FYI http://stackoverflow.com/a/18304517/448017.

What do you guys think?

@johnjelinek
Copy link
Author

Yea, I think primus + SockJS makes sense.

@ajohnclark
Copy link

+1 to SockJS after client side DDoSing server. Great seed though :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants