Class | Bunny::Queue |
In: |
lib/bunny/queue08.rb
|
Parent: | Qrack::Queue |
Queues store and forward messages. Queues can be configured in the server or created at runtime. Queues must be attached to at least one exchange in order to receive messages from publishers.
Acknowledges one or more messages delivered via the Deliver or Get-Ok methods. The client can ask to confirm a single message or a set of messages up to and including a specific message.
Binds a queue to an exchange. Until a queue is bound it will not receive any messages. Queues are bound to the direct exchange ’’ by default. If error occurs, a Bunny::ProtocolError is raised.
:bind_ok if successful.
Requests that a queue is deleted from broker/server. When a queue is deleted any pending messages are sent to a dead-letter queue if this is defined in the server configuration. Removes reference from queues if successful. If an error occurs raises Bunny::ProtocolError.
:delete_ok if successful
Gets a message from a queue in a synchronous way. If error occurs, raises Bunny::ProtocolError.
Hash {:header, :payload, :delivery_details}. :delivery_details is a hash {:consumer_tag, :delivery_tag, :redelivered, :exchange, :routing_key}.
If the queue is empty the returned hash will contain the values -
:header => nil :payload => :queue_empty :delivery_details => nil
N.B. If a block is provided then the hash will be passed into the block and the return value will be nil.
Removes all messages from a queue. It does not cancel consumers. Purged messages are deleted without any formal "undo" mechanism. If an error occurs raises Bunny::ProtocolError.
:purge_ok if successful
Removes a queue binding from an exchange. If error occurs, a Bunny::ProtocolError is raised.
:unbind_ok if successful.
Cancels a consumer. This does not affect already delivered messages, but it does mean the server will not send any more messages for that consumer.
:unsubscribe_ok if successful