Azure-sdk-for-net: [FEATURE REQ] Cancellation support for client.ReceiveAsync()

[SeanFeldman]

Is your feature request related to a problem? Please describe.

Azure Service Bus is using long-polling to retrieve messages. That means user code has to wait for command execution before an endpoint can shut down. With asynchronous libraries, it's a common theme and a recommended practice to pass a CancellationToken to invoke earlier termination of work.

Describe the solution you'd like

1. Add support for CancellationToken to ReceiveAsync()
2. Consider a review of the client to support cancellation pattern throughout various APIs (ReceiveAsync(), SendAsync(), AcceptMessageSessionAsync(), etc).

Describe alternatives you've considered

For the context, here's the original issue from the client's previous repository: https://github.com/Azure/azure-service-bus-dotnet/issues/439#issuecomment-423770087

[praries880]

https://github.com/Azure/autorest-clientruntime-for-java/pull/622

[SeanFeldman]

@praries880 the issue you've linked to seems to refer to something completely different than this issue is about. Was this a typo?

[jfggdl]

@axisc, would you please create an internal work item in our backlog to address Sean's concerns/feature request?

[axisc]

added this to the internal team backlog
https://msazure.visualstudio.com/One/_workitems/edit/5038388

[SeanFeldman]

@axisc closing public issues in favour of an internal backlog is not a good idea.
Please keep public issues open and close when the internal issues are completed.

[goenning]

I'm with @SeanFeldman on this one, I subscribe to notifications on feature requests that I need so I known when it's implemented. Ideally it should be done as Sean suggested, if not, at least post an update on this thread when it's implemented.

[danielmarbach]

@jfggdl @axisc Given the popularity of https://github.com/Azure/azure-service-bus-dotnet/issues/439#issuecomment-423770087 why isn't this reopened?

// cc @nemakam

[jfggdl]

Thanks for your feedback. We will keep this issue open and will update it once we have any news about the candidate feature to implement token cancellation support.

[jsquire]

Moving this to the backlog milestone, as the associated sprint has passed.

@axisc: Would you be so kind as to confirm that this is still an active item and help route to the appropriate individual?

[SebastianAchatz]

Is there any timeline for cancellation support in the client sdk?