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 looking at the code I'm wondering how to best handle web socket errors?
Here it throws an exception when a web socket error occurs.
If i'm not mistaking it will catch it here and log it without the library user being able to catch it?
If so, i guess the only way is to periodically compare ActiveWebSockets and AllSockets?
ActiveWebSockets
AllSockets
The text was updated successfully, but these errors were encountered:
Hi @trydis ,
We could add a callback in for errors if you would like, if they are getting swallowed by the underlying library?
Sorry, something went wrong.
I think that makes sense, especially since a connection is only valid for 24 hours.
A single connection to stream.binance.com is only valid for 24 hours; expect to be disconnected at the 24 hour mark
Is this still required?
No, not by me at least.
No branches or pull requests
Issue Overview
When looking at the code I'm wondering how to best handle web socket errors?
Here it throws an exception when a web socket error occurs.
If i'm not mistaking it will catch it here and log it without the library user being able to catch it?
If so, i guess the only way is to periodically compare
ActiveWebSockets
andAllSockets
?Package Version: 4.0.1
The text was updated successfully, but these errors were encountered: