Skip to content

Commit 4ad1795

Browse files
author
Simon MacMullen
committed
Correct comment. Bigger diff than seems necessary since Visual Studio screwed up line endings.
1 parent 68184cb commit 4ad1795

File tree

1 file changed

+24
-24
lines changed
  • projects/client/RabbitMQ.Client/src/client/api

1 file changed

+24
-24
lines changed

projects/client/RabbitMQ.Client/src/client/api/IModel.cs

Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -91,30 +91,30 @@ public interface IModel: IDisposable
9191
///exceptions thrown in ModelShutdownEventHandler delegates
9292
///etc.
9393
///</remarks>
94-
event CallbackExceptionEventHandler CallbackException;
95-
96-
///<summary>Signalled when an unexpected message is delivered
97-
///
98-
/// Under certain circumstances it is possible for a channel to receive a
99-
/// message delivery which does not match any consumer which is currently
100-
/// set up via basicConsume(). This will occur after the following sequence
101-
/// of events:
102-
///
103-
/// ctag = basicConsume(queue, consumer); // i.e. with explicit acks
104-
/// // some deliveries take place but are not acked
105-
/// basicCancel(ctag);
106-
/// basicRecover(false);
107-
///
108-
/// Since requeue is specified to be false in the basicRecover, the spec
109-
/// states that the message must be redelivered to "the original recipient"
110-
/// - i.e. the same channel / consumer-tag. But the consumer is no longer
111-
/// active.
112-
///
113-
/// In these circumstances, you can register a default consumer to handle
114-
/// such deliveries. If no default consumer is registered the delivery is
115-
/// ignored.
116-
///
117-
/// Most people will not need to use this.</summary>
94+
event CallbackExceptionEventHandler CallbackException;
95+
96+
///<summary>Signalled when an unexpected message is delivered
97+
///
98+
/// Under certain circumstances it is possible for a channel to receive a
99+
/// message delivery which does not match any consumer which is currently
100+
/// set up via basicConsume(). This will occur after the following sequence
101+
/// of events:
102+
///
103+
/// ctag = basicConsume(queue, consumer); // i.e. with explicit acks
104+
/// // some deliveries take place but are not acked
105+
/// basicCancel(ctag);
106+
/// basicRecover(false);
107+
///
108+
/// Since requeue is specified to be false in the basicRecover, the spec
109+
/// states that the message must be redelivered to "the original recipient"
110+
/// - i.e. the same channel / consumer-tag. But the consumer is no longer
111+
/// active.
112+
///
113+
/// In these circumstances, you can register a default consumer to handle
114+
/// such deliveries. If no default consumer is registered an
115+
/// InvalidOperationException will be thrown when such a delivery arrives.
116+
///
117+
/// Most people will not need to use this.</summary>
118118
IBasicConsumer DefaultConsumer { get; set; }
119119

120120
///<summary>Returns null if the session is still in a state

0 commit comments

Comments
 (0)