On 03/27/2013 01:34 PM, Rob Godfrey wrote:
So one question I would have is whether two implementations of the same API should not actually be the same component... Should we not just have a Qpid JMS component that currently has two released artefacts? Similarly the Qpid Messaging API may have a pure python implementation and the C++/Swigged versions. This seems analogous to how Proton is working with both a Java and a C implementation.
Yes, you are probably right. I personally tend to view the c++ and python messaging clients as two distinct components as though they aim to be similar there are still significant differences at present.
The most important question here is what the future plans are for the pure python implementation, particularly with regard to AMQP 1.0 support. It's probably true that however we answer that, long term there is one component here with different artefacts within it.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
