[rabbitmq-discuss] AMQP over HTTP proxy

Brett Cameron brett.r.cameron at gmail.com
Sun Apr 28 20:27:54 BST 2013


You might also want to look at https://github.com/tonyg/rabbithub, although
I would note that the code probably requires a little (very little)
tweaking to work with RabbitMQ 3.x

Brett


On Mon, Apr 29, 2013 at 6:49 AM, Gavin M. Roy <gmr at meetme.com> wrote:

>  In that case you might want to check out:
>
> 1. The Web Stomp plugin:
> http://www.rabbitmq.com/blog/2012/05/14/introducing-rabbitmq-web-stomp/
>
> 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 (http://www.json-rpc.org/). 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.
>
> Gavin
>
> On Sunday, April 28, 2013 at 2:40 PM, Tomer Paz wrote:
>
> one clarification:
> we do pub-sub, where the publisher is in the datacenter and the 'workers'
> app are distributed over remote sites connected via WAN.
> By "clients" I meant the worker apps.
>
> On Sunday, April 28, 2013 9:41:02 AM UTC+3, 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
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> 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/20130429/671af53d/attachment.htm>


More information about the rabbitmq-discuss mailing list