ReliablePublishingMessagingChannel

consumes Confirmation messages from the server, this should be used exclusively, or otherwise different instances compete over received values, and each get different set of values.

Consumes and decodes messages

Note that you MUST acknowledge (ack, reject, nack) messages if you select any ConsumeMode but ConsumeMode.RaiseOnError(false)

Consumes raw messages

Creates a message that is not mandatory, encodes and publishes it

Encodes and publishes a message that is not mandatory

Encodes and publishes an envelope, this is a low level operation and is exposed only for special circumstances, always prefer to use other higher level publish methods

Note that if a mandatory message fails in routing, it is returned to the client and you MUST also consume returned if you publish mandatory messages

Publishes raw message that is not mandatory This is useful if you have handled encoding and want to publish a raw message directly

Publishes raw envelope, this is a low level operation and is exposed only for special circumstances, always prefer to use other higher level publish methods

Note that if a mandatory message fails in routing, it is returned to the client and you MUST also consume returned if you publish mandatory messages

like publisherRaw, but encodes messages as well

A pipe that publishes Envelopes that may or may not be mandatory, And returns a delivery tag for every incoming message, and ReturnedMessageRaw for returned messages.

Note that this pipe SHOULD be used exclusively, as it is draining from the returned messages that is backed by a queue.

consumes returned messages from the server, this should be used exclusively, or otherwise different instances compete over received values, and each get different set of values.

Also note that this is a low level operation that is exposed for special circumstances, always prefer to use publisher pipe instead, unless necessary