[rabbitmq-discuss] Implementation / Specification Stability?

Landon Fuller landonf at threerings.net
Fri Oct 19 02:15:11 BST 2007


I'm investigating using AMQP and RabbitMQ as our service  
infrastructure backbone.

I've run into some interesting incompatibilities between Qpid at  
RabbitMQ --  an example:
	- Qpid does not support the Access Class
	- RabbitMQ's client API requires it
	- According to https://issues.apache.org/jira/browse/QPID-552, the  
Access class has been removed for 0-10, and replaced with sessions.

This leads to my questions:
	-- Is it crazy to hope for backwards compatibility with older  
clients as both the specification, and the RabbitMQ implementation,  
	-- Will RabbitMQ Java API compatibility be broken as the  
specification changes?

In other words, am I engaging in massive foot-shooting by trying to  
build on AMQP now, and should I exercise judicious patience?

Landon Fuller
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20071018/51b63456/attachment.pgp 

More information about the rabbitmq-discuss mailing list