Thank you for the help, Emile.<div><br></div><div>Our server-side client is an AMQP client in node.js (node-amqp) that connects directly to RabbitMQ. That's why I've mentioned that we have a "replyTo" queue and not a "reply-to" in that client. (We do send the message with a "reply-to" header in the STOMP client)</div>
<div><br></div><div>We've made progress and are now able to send back the reply from our server-side client. We figured out that a reply queue such as "/reply-queue/amq.gen-w2jykNGp4DNDBADm3C4Cdx" simply corresponds to the RabbitMQ queue "amq.gen-w2jykNGp4DNDBADm3C4Cdx" in the default exchange. Thus, we're now removing the "/reply-queue/" part of the replyTo header, and using the result as the destination queue for the response. We're assuming that this should/could be done transparently by an AMQP client with the notion that RPC messages from STOMP clients will need this replyTo string manipulation. Is this correct?</div>
<div><br></div><div>More details about a working solution can be found in this Stack Overflow answer:�<a href="http://stackoverflow.com/a/12591697">http://stackoverflow.com/a/12591697</a></div><div><br></div><div>Thank you,</div>
<div>Tiago</div><div><br><div class="gmail_quote">On Wed, Sep 26, 2012 at 11:08 AM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
On 24/09/12 15:14, Tiago Alves wrote:<br>
> (example: replyTo: '/reply-queue/amq.gen-w2jykNGp4DNDBADm3C4Cdx'). Still<br>
<br>
That not a recognised header instead of "replyTo" it should be "reply-to".<br>
<br>
> in my server-side client, I can reply to the message just by publishing<br>
> a message to "/reply-queue/amq.gen-w2jykNGp4DNDBADm3C4Cdx".<br>
<br>
Correct, assuming your server-side uses STOMP.<br>
<br>
> So, how do I subscribe to the reply-to queue? How can I get the results<br>
> of RPC calls?<br>
<br>
You don't have to - the subscription is made for you automatically when<br>
you use the "reply-to" header.<br>
<br>
I would suggest that you verify this by hand first and only then move on<br>
to confirming that it also works with your websockets library.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-Emile<br>
<br>
<br>
</font></span></blockquote></div><br></div>