AMQP Specification Transport
AMQP Specification Transport
AMQP Specification Transport
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>AMQP</strong> <strong>Specification</strong>.<br />
Link<br />
5.14.5 Command: 0x030a (release messages)<br />
Signature: release( options: map, first: sequence-no, last: sequence-no, mark-redelivered: bit )<br />
The release command is used to indicate that the specified range of incoming transfers will never be<br />
processed. Any continuation transfers within the specified range are ignored. For this command to have any<br />
effect, it MUST be sent before the identified transfers are acknowledged. The messages carried by the<br />
released transfer commands become available to the sender for future transfer to this or other sessions.<br />
Messages that have been released MAY subsequently be delivered out of order. Implementations SHOULD<br />
ensure that released messages keep their position with respect to undelivered messages of the same priority.<br />
Field Details:<br />
options: map<br />
options map (optional)<br />
first: sequence-no<br />
(required)<br />
The start of the incoming command range.<br />
last: sequence-no<br />
(optional)<br />
The end of the incoming command range. If not set then this is taken to be the same as first.<br />
mark-redelivered: bit<br />
mark the released messages as redelivered (optional)<br />
If the mark-redelivered flag is set, any messages released by this command MUST have the<br />
redelivered flag set according to the semantics specified in the delivery-properties definition.<br />
<strong>AMQP</strong> <strong>Transport</strong> v. 1-0 Page 59 of 83
Change language