[openamq-dev] reply_to and routing key

[Martin Sustrik]

Hi Mike,

Basically, AMQP allows different ways of routing messages. You can route
on routing-key - this is the most simple and fastest model. You can do
'content based routing', which means you can route messages on a table
of name-value pairs, which is slower but more powerful.

To get some idea about how the whole thing works, have a look at this
tutorial:

http://wiki.openamq.org/tutorial:understanding-amq-model

For content-based routing tutorial have a look here:

http://wiki.openamq.org/tutorial:content-based-routing

As for reply_to, it's different from routing_key and you shouldn't
bother with it. It's intended to JMS-over-AMQP application to implement
JMS-style RPC messaging.

Hope this helps.
Martin

On 3/11/2007, "Mike Owens" <mikeowens at gmail.com> wrote:

>I just discovered AMQ (and OpenAMQ) last night. I've been an avid open
>source uses for years, and it amazes me that this whole thing completely
>slipped through my radar. Wonderful, wonderful software guys.
>
>Anyway, I've been playing the the im_receiver/im_sender examples, and I have
>the receiver sending back the message to the sender. The problem is, the
>only way I've been able to do this is by having the sender explicitly set
>the routing-key in the content's reply_to property. It seems to me that
>there would be some way for the receiver to obtain this information from the
>content without the sender having to provide it. Again, this may be well
>documented in the specs, but I'm still getting acquainted.
>Thanks