/usr/lib/ruby/1.8/bunny/subscription09.rb is in libbunny-ruby1.8 0.6.2-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 | module Bunny
=begin rdoc
=== DESCRIPTION:
Asks the server to start a "consumer", which is a transient request for messages from a specific
queue. Consumers last as long as the channel they were created on, or until the client cancels them
with an _unsubscribe_. Every time a message reaches the queue it is passed to the _blk_ for
processing. If error occurs, _Bunny_::_ProtocolError_ is raised.
==== OPTIONS:
* <tt>:consumer_tag => '_tag_'</tt> - Specifies the identifier for the consumer. The consumer tag is
local to a connection, so two clients can use the same consumer tags. If this option is not
specified a server generated name is used.
* <tt>:ack => false (_default_) or true</tt> - If set to _false_, the server does not expect an
acknowledgement message from the client. If set to _true_, the server expects an acknowledgement
message from the client and will re-queue the message if it does not receive one within a time specified
by the server.
* <tt>:exclusive => true or false (_default_)</tt> - Request exclusive consumer access, meaning
only this consumer can access the queue.
* <tt>:nowait => true or false (_default_)</tt> - Ignored by Bunny, always _false_.
* <tt>:timeout => number of seconds - The subscribe loop will continue to wait for
messages until terminated (Ctrl-C or kill command) or this timeout interval is reached.
* <tt>:message_max => max number messages to process</tt> - When the required number of messages
is processed subscribe loop is exited.
==== OPERATION:
Passes a hash of message information to the block, if one has been supplied. The hash contains
:header, :payload and :delivery_details. The structure of the data is as follows -
:header has instance variables -
@klass
@size
@weight
@properties is a hash containing -
:content_type
:delivery_mode
:priority
:payload contains the message contents
:delivery details is a hash containing -
:consumer_tag
:delivery_tag
:redelivered
:exchange
:routing_key
If the :timeout option is specified then Qrack::ClientTimeout is raised if method times out
waiting to receive the next message from the queue.
==== EXAMPLES
my_queue.subscribe(:timeout => 5) {|msg| puts msg[:payload]}
my_queue.subscribe(:message_max => 10, :ack => true) {|msg| puts msg[:payload]}
=end
class Subscription09 < Qrack::Subscription
def setup_consumer
client.send_frame(
Qrack::Protocol09::Basic::Consume.new({ :deprecated_ticket => 0,
:queue => queue.name,
:consumer_tag => consumer_tag,
:no_ack => !ack,
:exclusive => exclusive,
:nowait => false}.merge(@opts))
)
method = client.next_method
client.check_response(method, Qrack::Protocol09::Basic::ConsumeOk,
"Error subscribing to queue #{queue.name}")
@consumer_tag = method.consumer_tag
end
end
end
|