-
Notifications
You must be signed in to change notification settings - Fork 57
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
how to close client #81
Comments
I use 3.0.4 version |
looks like we need try/catch around the Socket Read code to handle the case where the low level socket has been closed in the Close() function |
@RogerHardiman I'm facing the same issue, same version. Any updates on this? I'm currently diving in so any guidance is appreciated. Happy to submit a PR or report back here if I find anything. On that note - does this error mean that the connection has already closed? In my initial proof-of-concept implementation, I just decided to never close any of the connections, which seemed wrong. Do you see any side-effects coming of that, or you think I'm safe to just ignore? Thank you btw, this library has greatly helped. |
@meesii is this now functional? please share workaround if you found one. |
I have created a branch called teardown. Thanks |
When I need to close the client, I call the close method, but the program reports an error.
The text was updated successfully, but these errors were encountered: