[rabbitmq-discuss] AMQP over HTTP proxy

[Gavin M. Roy]

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. 

https://github.com/gmr/statelessd

Gavin 


On Sunday, April 28, 2013 at 2:41 AM, Tomer Paz wrote:

> Hi,
> 
> We have strict constraint to use "web services" between distributed worker apps on remote sites communicating over WAN.
> meaning - worker apps must use only HTTP port 80 to communicate with Rabbit broker.
> These WAN connections are low quality in some cases...
> 
> What is the best practice recommended?
> WebSockets? native or over STOMP?
> 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)
> 
> Our clients are mostly written in .Net and Java, they are apps, not browsers (just to clarify the issue)
> 
> TIA
> Tomer
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com (mailto:rabbitmq-discuss at lists.rabbitmq.com)
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130428/f7dd6a41/attachment.htm>