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.7 Command: 0x030c (unpark messages)<br />
Signature: unpark( options: map, mode: unpark-mode, first: sequence-no, last: sequence-no )<br />
The unpark command is used to indicate that the specified range of incoming transfers should no longer be<br />
held on the link. The unpark-mode defines what should be done with the held messages. They may be<br />
acknowledged, released back to the queue, rejected, or resent on the same link. Any continuation transfers<br />
within the specified range are ignored.<br />
Field Details:<br />
options: map<br />
options map (optional)<br />
mode: unpark-mode<br />
(required)<br />
One of acknowledge, reject, release, resend. If resend is chosen for a message whose link has<br />
subsequently been deleted, the message will be released instead of resent.<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 />
5.14.8 unpark-mode: uint8 (unpark behaviors)<br />
Valid values:<br />
0 (acknowledge)<br />
1 (reject)<br />
2 (release)<br />
3 (resend)<br />
5.15 Message Format<br />
5.15.1 message-properties struct (immutable properties of the message)<br />
Message properties carry information about the message.<br />
Field Details:<br />
message-id: vbin16<br />
application message identifier (optional)<br />
<strong>AMQP</strong> <strong>Transport</strong> v. 1-0 Page 61 of 83
Change language