<div>
If you want to publish over HTTP only, you might want to check out statelessd. It's a HTTP publishing daemon that allows for scale-out front-ends to be load-balanced. Works very well for me. I should package it up and put it on pypi soon, but I need to get the required pika 0.9.13 pushed first. You'll need to use github master of Pika if you want reconnections and such to work right.
</div><div><br></div><div><a href="https://github.com/gmr/statelessd">https://github.com/gmr/statelessd</a></div><div><br></div><div>Gavin</div>
<div></div>
<p style="color: #A0A0A8;">On Sunday, April 28, 2013 at 2:41 AM, Tomer Paz wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><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><div><div>_______________________________________________</div><div>rabbitmq-discuss mailing list</div><div><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a></div><div><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>