The default exchange is a direct exchange and the bindings are
forced to match exactly with the existing queue names. It is a
workaround for the fact that AMQP forces you to send to an exchange
whether you want to or not.
What is it you actually want to achieve? The only thing you can do
by sending messages to the default exchange is send them to a queue
(or have them dropped).
A Sender for the default exchange may be useful in case you want to
send to many different queues using one Sender and a different routing
key for each message. For instance when sending responses to reply-to
queues in a request-response pattern.
I'm working on a AMQP vendor-neutral C++ API and I'm trying to stay as
close to the concepts and ideas of the AMQP specs as possible. I guess
sending to the default exchange is a completely sane thing to do.
Let's say I create a Sender for queue A. It will actually point to the
default exchange with the routing key defaulting to A, right?
What happens if I use this sender to send a message with subject being
set to B? Will the message go to queue B?
Cheers
Jiri
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
