-
Notifications
You must be signed in to change notification settings - Fork 781
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
[feature] Provide cancellation token in AcceptMessageSession #293
Comments
It's not just This is an issue with the client in general. I've tried to convince here, but it didn't happen. With the client moving to a new repository, I'll raise it there (Azure/azure-sdk-for-net#6653), which you can upvote if you'd like. Either way, it belongs to https://github.com/Azure/azure-sdk-for-net/ |
I'd like to add my support to this as well. I have a message queue feeding a constrained resource, and from time to time that resource will issue an alert that it needs to stop processing for a time. I have to close the QueueClient at that point, but the message pumps keep functioning despite the client being closed, which causes a lot of noise. |
Same here, we should be able to suspend the message pump without closing the client (sending should still be possible) |
If this issue still occurs using the latest SDK, please let us know and we can re-open the issue. |
Method AcceptMessageSession should make a usage of cancellation.
AcceptMessageSession (TimeSpan, CancellationToken)
Following code could be in this case simplified:
With cancellation:
The text was updated successfully, but these errors were encountered: