2009/3/20 Robert Godfrey <[email protected]>: >> Our Java JMS clients interoperate with clients in Python and C++. There's >> clearly demand for Java JMS support. I would like to also see a Java client >> that more directly reflects AMQP, as our clients in other languages do. >> > > I must admit see no real reason for this *unless* > 1) there is defined some common AMQP API that is not JMS and is > blessed by the AMQP working group, or > 2) there are significant features of AMQP than cannot be comfortably > accessed through JMS or obvious extensions. > > Writing proprietary APIs for basic messaging functionality seems like > a giant step backwards.
Completely agree 110%. (As regular readers of this column will know :-)). > It seems that in the other languages we are moving towards a more > protocol-neutral API. I don't see any reason to move in the reverse > direction for Java. Yes surely the changes between 0-10 and 1-0 have illustrated to anyone who was still not convinced that APIs that are not protocol neutral are a complete nightmare from a backwards compatibility perspective. JMS may not be perfect but I can just about guarantee that most of the apps written in Java for Qpid using the JMS API will work just fine when we release a Qpid broker than supports the 1-0 protocol. Who's feeling confident about Python?? RG --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
