<div dir="ltr"><div>You might also want to look at <a href="https://github.com/tonyg/rabbithub">https://github.com/tonyg/rabbithub</a>, although I would note that the code probably requires a little (very little) tweaking to work with RabbitMQ 3.x<br>
<br></div>Brett<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 29, 2013 at 6:49 AM, Gavin M. Roy <span dir="ltr"><<a href="mailto:gmr@meetme.com" target="_blank">gmr@meetme.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
In that case you might want to check out:</div><div><br></div><div>1. The Web Stomp plugin:�<a href="http://www.rabbitmq.com/blog/2012/05/14/introducing-rabbitmq-web-stomp/" target="_blank">http://www.rabbitmq.com/blog/2012/05/14/introducing-rabbitmq-web-stomp/</a></div>
<div><br></div><div>2. If web sockets won't work for you, the experimental json-rpc plugin that ships with RabbitMQ.�As the name implies, it allows for AMQP over JSON-RPC (<a href="http://www.json-rpc.org/" target="_blank">http://www.json-rpc.org/</a>).�The core methods are cast and call. �Unfortunately the code is the best place I found for documentation about using the JSON RPC protocol.�There is also a plugin that has an example JavaScript client using it.</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div>Gavin</div></font></span><div><div class="h5">
<div></div>
<p style="color:#a0a0a8">On Sunday, April 28, 2013 at 2:40 PM, Tomer Paz wrote:</p>
</div></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px">
<span><div><div><div class="h5"><div>one clarification:<div>we do pub-sub, where the publisher is in the datacenter and the 'workers' app are distributed over remote sites connected via WAN.</div>
<div>By "clients" I meant the worker apps.<br><br>On Sunday, April 28, 2013 9:41:02 AM UTC+3, Tomer Paz wrote:<blockquote type="cite"><div>Hi,<br><br>We have strict constraint to use "web services" between distributed worker apps on remote sites communicating over WAN.<br>
meaning - worker apps must use only HTTP port 80 to communicate with Rabbit broker.<br>These WAN connections are low quality in some cases...<br><br>What is the best practice recommended?<br>WebSockets? native or over STOMP?<br>
Assume we are using a proxy HTTP server at the data-center, where Rabbit hides behind it. (currently Apache HTTPD, if that is relevant at all)<br><br>Our clients are mostly written in .Net and Java, they are apps, not browsers (just to clarify the issue)<br>
<br>TIA<br>Tomer<br></div></blockquote></div></div></div></div><div><div>_______________________________________________</div><div class="im"><div>rabbitmq-discuss mailing list</div><div><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a></div>
<div><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></div></div></div></div></span>
</blockquote>
<div>
<br>
</div>
<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>
<br></blockquote></div><br></div></div></div>