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
request_id
When a subscription is closed, all the subscriptions are iterated over and returns once a closed subscription is found, which is inefficient and could close the wrong subscription if "several are closed at the same time", see https://github.com/paritytech/jsonrpsee/blob/v2/src/client/ws/client.rs#L303-#L309
Thus, it would be better to just have ChannelClosed(RequestId) than it could be performed in constant time and is correct.
ChannelClosed(RequestId)
The text was updated successfully, but these errors were encountered:
fix(ws client): embed request id SubscriptionClose
24c921f
Fixes #169
fix(ws client): embed request id SubscriptClosed
0aaf5b7
SubscriptionClosed
fix(ws client): embed request id in SubscriptionClosed (#170)
a08f012
* fix(ws client): embed request id SubscriptClosed Fixes #169 * Update src/client/ws/client.rs * Update src/client/ws/client.rs Co-authored-by: David <dvdplm@gmail.com> * Update src/client/ws/client.rs Co-authored-by: David <dvdplm@gmail.com> Co-authored-by: David <dvdplm@gmail.com>
6165656
No branches or pull requests
When a subscription is closed, all the subscriptions are iterated over and returns once a closed subscription is found, which is inefficient and could close the wrong subscription if "several are closed at the same time", see https://github.com/paritytech/jsonrpsee/blob/v2/src/client/ws/client.rs#L303-#L309
Thus, it would be better to just have
ChannelClosed(RequestId)
than it could be performed in constant time and is correct.The text was updated successfully, but these errors were encountered: