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 />
Connection<br />
TCP Client<br />
TCP Server<br />
===============================================<br />
TCP-CONNECT<br />
TCP-ACCEPT<br />
PROTO-HDR<br />
PROTO-HDR<br />
OPEN ---+ +--- OPEN<br />
\ /<br />
pipelined cmd/ctl x pipelined cmd/ctl *<br />
/ \<br />
proceed proceed<br />
...<br />
-----------------------------------------------<br />
* Note that a peer's use of pipelined<br />
commands and/or controls cannot be<br />
observed by the partner so long as the<br />
pipelined commands and controls conform<br />
to the partner's capabilities and<br />
limitations.<br />
3.4 Closing a Connection<br />
Prior to closing a connection, each peer must write a close control with a code indicating the reason for<br />
closing. This control must be the last thing ever written onto a connection. After writing this control the peer<br />
should continue to read from the connection until it receives the partner's close control.<br />
TCP Client<br />
TCP Server<br />
=============================<br />
...<br />
CLOSE -------><br />
+-- CLOSE<br />
/ TCP-CLOSE<br />
TCP-CLOSE
Change language