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 />
incoming-locales: str16<br />
desired locales for incoming text in decreasing level of<br />
preference (multiple)<br />
A list of locales that the sending peer permits for incoming informational text. This list is<br />
ordered in decreasing level of preference. The receiving partner will chose the first (most<br />
preferred) incoming locale from those which it supports. If none of the requested locales are<br />
supported, en_US will be chosen. Note that en_US need not be supplied in this list as it is<br />
always the fallback. A peer may determine which of the permitted incoming locales is chosen<br />
by examining the partner's supported locales as specified in the outgoing-locales field.<br />
peer-properties: map<br />
peer properties (optional)<br />
The properties SHOULD contain at least these fields: "product", giving the name of the client<br />
product, "version", giving the name of the client version, "platform", giving the name of the<br />
operating system, "copyright", if appropriate, and "information", giving other general<br />
information.<br />
Definition: MIN-MAX-FRAME-SIZE<br />
Value: 4096<br />
Description: the minimum size (in bytes) of the maximum frame size<br />
During the initial connection negotiation, the two peers must agree upon a maximum frame size. This<br />
constant defines the minimum value to which the maximum frame size can be set. By defining this value,<br />
the peers can guarantee that they can send frames of up to this size until they have agreed a definitive<br />
maximum frame size for that connection.<br />
<strong>AMQP</strong> <strong>Transport</strong> v. 1-0 Page 15 of 83
Change language