-
Notifications
You must be signed in to change notification settings - Fork 61
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
disconnected loop while waiting for redial only after first retry #38
Comments
Note: my ws server was running on port X, but my recws client was pointing to port Y |
must be like this
|
Open
@nikepan please keep in mind that sleeping for a certain amount of time will never be a reliable solution |
This sleep not for pause. Only for release cpu and throttle messages. But I will try make it without sleep. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code (from example, but use ws rather than wss)
The server is a raw ws nodejs app, working perfectly with a golang client using gorilla websocket.
14:25:30 => 14:25:32 = OK, waiting
14:25:32 => 14:25:34 = disconnected loop ?
14:25:34 = closing
The text was updated successfully, but these errors were encountered: