I'm currently using Qpid 0.8 which uses AMQP 0.10 We're about to start using it pretty seriously and we'll have a fair number of clients connecting. I'm conscious that I've been arguing for a design that in effect introduces a significant degree of coupling, which is kind of ironic as it's logically a pretty decoupled pattern.
What I really mean is that the client systems all have to use one or other AMQP client runtime (they will most likely be using Qpid with some possibly using Camel's AMQP). So everything will be fine and dandy in the short term as we'll have AMQP 0.10. What's going to happen when AMQP 1.0 comes along? So as a scenario I might rather like to upgrade the broker to v1.0, but I really really don't want to have a massive dependency that would force all clients to upgrade in lock-step. That would be a massive failing for a messaging system that was all about introducing a high level of decoupling into the Enterprise. So I'm assuming that when support for AMQP v1.0 is introduced AMQP v0.10 support will be retained for some period to give a degree of backwards compatibility and avoid this scenario. It would be great to have a statement to that effect from the dev team. regards fadams -- View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/Backwards-compatibility-when-AMQP-V1-0-come-online-tp6158663p6158663.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
