Cancellation

What is the purpose of cancellation tokens in methods like Publish or Request? Example:

 public class TestConsumer : IConsumer<Person>
      {
          public async Task Consume(ConsumeContext<Person> context)
          {
              await Task.Delay(10000, context.CancellationToken);
              context.CancellationToken.ThrowIfCancellationRequested();
              context.Respond(new PersonResponse() { Name = "SAD" });
          }
      }

 IRequestClient<Person, PersonResponse> client = busControl.CreatePublishRequestClient<Person, PersonResponse>(TimeSpan.FromSeconds(30));
            var cts = new CancellationTokenSource();

            Task.Run(async () =>
            {
                await Task.Delay(3000);
                cts.Cancel();
            });

            var c = await client.Request(new Person() { Name = "ELO" }, cts.Token);

In ‘Consume’ method I would expect to throw an exception. Is there anything I am missing here? How should we handle it? Should we build our own mechanism?

[phatboyg]

When calling Publish and passing a cancellationToken, if you no longer want to wait for the message to be published, you can cancel the operation.

In the case of consuming a message, the CancellationToken is controlled by the transport, and if the transport fails or triggers a cancellation, it will set the cancellationToken to Cancel.

[phatboyg]

Cancellation of the request from the client side is not going to cancel the consumer on the receive endpoint. The only times that the consumeContext CancellationToken is set is when the transport aborts the message, which almost never happens. Once the message is sent from the client to RabbitMQ, the only thing that is cancelled is the wait on the client side.