You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2019. It is now read-only.
Right after my client connects to the server, it sends a message.
Most of the time server doesn't handle this message. My guess is that session is created a bit too late
(I checked, and WebSocketServer.NewSessionConnected is sometimes invoked later than client sends the message)
Anyone had similar problems? How did you work around them?
The text was updated successfully, but these errors were encountered:
alvyxaz
changed the title
Message not handled right after connecting
Message not received right after connecting
Aug 21, 2016
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right after my client connects to the server, it sends a message.
Most of the time server doesn't handle this message. My guess is that session is created a bit too late
(I checked, and WebSocketServer.NewSessionConnected is sometimes invoked later than client sends the message)
Anyone had similar problems? How did you work around them?
The text was updated successfully, but these errors were encountered: