<div dir="ltr">A few other thoughts on your topology. Take a strong look at the routing keys and exchanges and queues. Rabbit's really designed to be a "asynchronous" messaging platform. I'm not sure though I understand what you mean by clients as well. Is the system doing the request to the stomp API your client? And it's also the client that wants to consume from the queue in an RPC kinda mechanism? What you could do in this case, would be startup a consumer in your process with a generated random value (e.g. machine name and datetime), the WEB STOMP publishes to a direct exchange with a message that includes a header "Return data to queue <randomvalue>". Your server side processing receives that message, processes it, reads that header and publishes a message to that queue. Then your consumer "thread" after your publisher is ready can just deliver the resulting message, and auto-delete the queue. Just one possibility.<div>
<br></div><div>Jason</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 11, 2013 at 5:49 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"><br>
Hi Magnus,<br>
<br>
Apologies for the delayed response to your query.<br>
<div class="im"><br>
On 28/09/13 22:18, Magnus Andersson wrote:<br>
<br>
> I need to get a handle on the routing key for the generated temporary<br>
> queue when using web stomp. I can't get that from the JavaScript side.<br>
<br>
</div>If you need the name of a temporary queue then that is normally a sign<br>
that you should name the queue yourself instead of relying on a<br>
server-generated name.<br>
<div class="im"><br>
> My desired scenario for my event driven app.<br>
> 1) Browser client opens a websocket connection to rabbitmq web stomp<br>
> 2) When calling client.connect, the routing key is made available<br>
</div>> (example: amq.gen-oQVllULAASDvZdXsxFADHg). *Not working today?*<br>
<br>
Opening a connection does not involve a routing key.<br>
<div class="im"><br>
> There is a fan-out exchange that all clients subscribe to. But I mostly<br>
> want to send messages to one dedicated client at a time.<br>
<br>
</div>If you want to address clients individually then the clients should<br>
maintain separate individual subscriptions for that line of<br>
communication, possibly not involving temporary queue names.<br>
<div class="im"><br>
> The documentation is very scarce on Web Stomp and I'm new to RabbitMQ<br>
> and not particularly Erlang proficient. So I need some pointers.<br>
<br>
</div>There are some examples that illustrate use of the plugin:<br>
<br>
<a href="http://hg.rabbitmq.com/rabbitmq-web-stomp-examples/" target="_blank">http://hg.rabbitmq.com/rabbitmq-web-stomp-examples/</a><br>
<br>
<br>
<br>
<br>
<br>
-Emile<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Jason McIntosh<br><a href="https://github.com/jasonmcintosh/">https://github.com/jasonmcintosh/</a><br>573-424-7612</div>
</div>