[rabbitmq-discuss] http://www.theserverside.com/news/thread.tss?thread_id=49013

[Alexis Richardson]

Blimey!

Thanks Neil.  I met these guys at MuleCon.  Admittedly it was late and
a little dark...  Nevertheless they took the view that JMS was somehow
more generally useful than a protocol and anyone defending protocols
was "taking a very narrow view".  Charitably, this could mean "I need
a model and an API in order to program" - but then the community has
integrated RabbitMQ with Mule and other platforms!  Uncharitably, one
might point out that HTTP, TCP, XMPP, FTP, ... are all good examples
of why protocols beat APIs.

I would be grateful if folks wanted to chip in on the TSS forums: on
the subject of why AMQP is a good thing.  Please, if you do, respect
that JMS has been around for a while and is good for many tasks!

Carl, Martin, Rob, .. that includes you guys too :-)

alexis


On Fri, Apr 11, 2008 at 1:49 PM, Neil Ellis <neil.ellis at mangala.co.uk> wrote:
>
> Someone may wish to respond to:
>
> I learn about AMQP at Mulecon. AMQP is a protocol-level standards initiative
> to provide a messaging infrastructure. Jahan told me, "AMQP tries to do
> something very important but may not be attainable. Because they are at the
> protocol level they may wind up being extensions on the side. I would bet on
> the JMS side."
>
> http://www.theserverside.com/news/thread.tss?thread_id=49013
> _______________________________________________
>  rabbitmq-discuss mailing list
>  rabbitmq-discuss at lists.rabbitmq.com
>  http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>



-- 
Alexis Richardson
+44 20 7617 7339 (UK)
+44 77 9865 2911 (cell)
+1 650 206 2517 (US)