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

Naught + Socket.io #55

Open
wpottier opened this issue Aug 27, 2014 · 4 comments
Open

Naught + Socket.io #55

wpottier opened this issue Aug 27, 2014 · 4 comments

Comments

@wpottier
Copy link

Hi,

I try to use naught on my project. This project was a webapp with an extensive use of websocket connection based on the lib socket.io.

The code works well when I use recluster for multiple worker but with naught the websocket connection is really unstable (many failed and disconnect).

Have you ever seen this behavior?

Thanks a lot for your help

@andrewrk
Copy link
Owner

andrewrk commented Dec 4, 2014

I just tested naught with websockets and it worked fine.

@vishy1618
Copy link

The reason AFAICT is because the new socket.io relies on sticky sessions for multi-node support (see http://socket.io/docs/using-multiple-nodes/).

Is there a possibility of adding support for sticky sessions?

@wamatt
Copy link

wamatt commented Feb 11, 2015

Are sticky sessions supported?

@majgis
Copy link

majgis commented Nov 13, 2015

Lack of support for sticky websocket sessions is the only feature keeping me from using naught. Would you consider adding support or accept a pull request using sticky-session or sticky-cluster?

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

5 participants