We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I connect to WS server from js, the connection is automatically closed. I tried with and without stand alone.
dispatcher = new WebSocketRails('0.0.0.0:3001/websocket', false); // false nor true dispacheer.trigger("some_message", {});
log
I [2016-08-08 12:28:13.575] [ConnectionManager] Connection opened: #<Connection::8073ec3ee09b5daa81fa> I [2016-08-08 12:28:13.582] [ConnectionManager] Connection closed: #<Connection::8073ec3ee09b5daa81fa>
Also, the state of the dispatcher is connectionall the time.
connection
websocket-rails (0.7.0) faye-websocket (0.10.0) websocket-rails-js (0.0.1)
The text was updated successfully, but these errors were encountered:
I actually have the same issue and cannot figure out why. I've been using this gem before with no problem.
Sorry, something went wrong.
Me too :/
I found the solution, what you need is that : https://github.com/phlegx/websocket-rails/tree/bugfix/388-latest-faye-websocket and that : https://github.com/moaa/websocket-rails/tree/sync_fixes
I merged those 2 commits in a custom repository and it works fine now.
Thanks @Uelb, i'll try that!
Can you tell me if passenger+nginx are a event machine? it will be necessary the standalone config?
No branches or pull requests
When I connect to WS server from js, the connection is automatically closed.
I tried with and without stand alone.
log
Also, the state of the dispatcher is
connection
all the time.websocket-rails (0.7.0)
faye-websocket (0.10.0)
websocket-rails-js (0.0.1)
The text was updated successfully, but these errors were encountered: