On Thu, Jan 3, 2013 at 9:16 AM, Chip Childers <chip.child...@sungard.com> wrote: > On Thu, Jan 3, 2013 at 1:31 AM, Murali Reddy <murali.re...@citrix.com> wrote: >> On 03/01/13 12:33 AM, "David Nalley" <da...@gnsa.us> wrote: >>>Interesting stuff. How and why did you decide on RabbitMQ? >> >> David, >> >> Default plug-in I am adding for event bus assumes AMQP. I have used >> RabbitMQ AMQP client. But the AMQP server it self could be any >> implementation of AMQP. Though I have not tested, RabbitMQ AMQP client is >> interoperable with Qpid [1] >> >> [1] http://www.rabbitmq.com/interoperability.html > > AMQP versions matter quite a bit actually. The Rabbit interop testing > is against Qpid 0.6, while the latest apache qpid release is 0.18. > AMQP isn't quite stable enough to assume that even the basic messaging > mechanics are the same really. > > That doesn't mean that a Rabbit MQ implementation isn't good to > have... it just means that it's not necessarily going to work with > every other AMQP broker implementation (or specific version). >
Yes, Sadly 'AMQP Implementation 1' != 'AMQP Implementation 2'. Take a look at the efforts the Red Hat folks had to undergo when making OpenStack (designed to work with RabbitMQ) work with Qpid - it appeared non-trivial to an outsider.
