<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, Pete!<br>
<br>
Yes, indeed the RabbitMQ currently uses the same value for the
exchange name and routing key. Also only the '/' vhost can be used
for the moment, as it is hardcoded in the code. But this module is
still under development and any new ideas are welcome.<br>
<br>
Regards,<br>
<pre class="moz-signature" cols="72">--
Răzvan Crainea
OpenSIPS Developer</pre>
<br>
On 11/30/2011 01:52 PM, Pete Kelly wrote:
<blockquote
cite="mid:CAEWH9M_k8e4zxpWaQ-Sqc8qmPW=K=pZnHTaHfnRPPyosZ59iKg@mail.gmail.com"
type="cite">Hi
<div><br>
</div>
<div>I have a question about the RabbitMQ functionality.</div>
<div><br>
</div>
<div>The documentation states that the 'exchange' will also be
used as the 'queue' used in RabbitMQ.</div>
<div><br>
</div>
<div>In my experience you do not send messages directly to a queue
in RabbitMQ, you send message which contains</div>
<div><br>
</div>
<div>- exchange name</div>
<div>- routing key</div>
<div>- message payload </div>
<div>
<br>
</div>
<div><br>
</div>
<div>RabbitMQ then uses the routing key to route the message to
the correct queue (or onward exchange).</div>
<div><br>
</div>
<div>Can you tell me if the RabbitMQ implementation supports this,
as it sounds like it does not currently... it seems it uses the
exchange as the routing key as well as exchange?</div>
<div><br>
</div>
<div>Pete</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</body>
</html>