amqplib transport.
copyright: |
|
---|---|
license: | BSD, see LICENSE for more details. |
Wait for an event on a channel.
Close the AMQP broker connection.
Establish connection to the AMQP broker.
request a connection close
This method indicates that the sender wants to close the connection. This may be due to internal conditions (e.g. a forced shut-down) or due to an error handling a specific method, i.e. an exception. When a close is due to an exception, the sender provides the class and method id of the method which caused the exception.
RULE:
After sending this method any received method except the Close-OK method MUST be discarded.
RULE:
The peer sending this method MAY use a counter or timeout to detect failure of the other peer to respond correctly with the Close-OK method.
RULE:
When a server receives the Close method from a client it MUST delete all server-side resources associated with the client’s context. A client CANNOT reconnect to a context after sending or receiving a Close method.
reply_code: short
The reply code. The AMQ reply codes are defined in AMQ RFC 011.
reply_text: shortstr
The localised reply text. This text can be logged as an aid to resolving issues.
class_id: short
failing method class
When the close is provoked by a method exception, this is the class of the method.
method_id: short
failing method ID
When the close is provoked by a method exception, this is the ID of the method.
Wait for an event on a channel.
Wait for a method that matches our allowed_methods parameter (the default value of None means match any method), and dispatch to it.
Convert encoded message body back to a Python value.
Encapsulate data into a AMQP message.