[rabbitmq-discuss] consume messages from exchanges
mikeb at rabbitmq.com
Tue Nov 16 12:04:51 GMT 2010
> Can anybody explain me some variables:
If passive=true, the server will check only that the named exchange or
queue is present, and raise an error if not. Note the contrast with
passive=false, for which an error is raised if the exchange or queue
*is* present *but* has different properties.
There's two places "exclusive" is used.
In queue.declare, it restricts the scope of the queue to the connection;
i.e., only the current connection will be able to refer to it. The one
exception to this is sending to the default exchange, where an exclusive
queue name may be given as the routing key.
In basic.consume, it ensures that the connection is the only consumer
from the given queue.
"nowait" means the server should not send a reply to an otherwise
synchronous method, e.g., queue.declare. It sounds useful, but often
there's important information in server responses (including the
presence of the response).
> W dniu 2010-11-15 20:25, Marek Majkowski pisze:
>> On Mon, Nov 15, 2010 at 11:43, Adam Kaminiecki<adamka at dgt.com.pl> wrote:
>>> I have got few questions about consumming practises.
>>> Which is better, create new consumer for each queues and exchanges when
>>> binding or Can I use 1 consumer?
>> You can't create 'a consumer for an exchange'.
>> Except from that, that's pretty common question. It all depends on your
>> design. Often you can have a single queue with one consumer
>> and a whole bunch of exchanges and bindings. The other time
>> it might be better to have a single exchange and many queues.
>> That's the whole point of AMQP, you can create topology as you need it.
>> So start with something simple, that you feel comfortable with.
>>> How can I change consumer name which is displayed when using rabbimqctl
>>> -q list_consumers? Is it possible??
>>> Can I use 1 consumer queue to bind it to more than 1 exchange?
>> Yes, a queue can have multiple bindings.
>> BTW, have you seen our tutorials?
More information about the rabbitmq-discuss