3030//---------------------------------------------------------------------------
3131
3232using System . Threading . RateLimiting ;
33- using RabbitMQ . Client . Impl ;
3433
3534namespace RabbitMQ . Client
3635{
@@ -41,11 +40,24 @@ public sealed class CreateChannelOptions
4140 {
4241 /// <summary>
4342 /// Enable or disable publisher confirmations on this channel. Defaults to <c>false</c>
43+ ///
44+ /// Note that, if this is enabled, and <see cref="PublisherConfirmationTrackingEnabled"/> is <b>not</b>
45+ /// enabled, the broker may send a <c>basic.return</c> response if a message is published with <c>mandatory: true</c>
46+ /// and the broker can't route the message. This response will not, however, contain the publish sequence number
47+ /// for the message, so it is difficult to correlate the response to the correct message. Users of this library
48+ /// could add the <see cref="Constants.PublishSequenceNumberHeader"/> header with the value returned by
49+ /// <see cref="IChannel.GetNextPublishSequenceNumberAsync(System.Threading.CancellationToken)"/> to allow correlation
50+ /// of the response with the correct message.
4451 /// </summary>
4552 public bool PublisherConfirmationsEnabled { get ; set ; } = false ;
4653
4754 /// <summary>
4855 /// Should this library track publisher confirmations for you? Defaults to <c>false</c>
56+ ///
57+ /// When enabled, the <see cref="Constants.PublishSequenceNumberHeader" /> header will be
58+ /// added to every published message, and will contain the message's publish sequence number.
59+ /// If the broker then sends a <c>basic.return</c> response for the message, this library can
60+ /// then correctly handle the message.
4961 /// </summary>
5062 public bool PublisherConfirmationTrackingEnabled { get ; set ; } = false ;
5163
0 commit comments