As a general design point, HTTP is designed around the idea of opening a
connection, doing one thing, and closing it. AMQP is designed around the
idea of opening a connection, doing lots of things for a while, then
closing it.
So AMQP connections are generally more expensive than HTTP requests. You
will likely do well if you can set up a gateway that has a few long
running pooled AMQP connections to use when handling HTTP requests.
PHP is of course badly suited to doing that sort of thing. Perl / python
I don't know, might not be much better. Java or .NET might be reasonable
to look at. Or Erlang of course :-)
Cheers, Simon
> --
> You received this message because you are subscribed to the Google
> Groups "rabbitmq-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
rabbitmq-user...@googlegroups.com
> <mailto:
rabbitmq-user...@googlegroups.com>.
> To post to this group, send email to
rabbitm...@googlegroups.com
> <mailto:
rabbitm...@googlegroups.com>.
> For more options, visit
https://groups.google.com/d/optout.