Gordon Sim wrote > Is there a particular reason for that choice? (The swigged > qpid_messaging is not really a first-class client. It was more of an > internal convenience for writing tests etc).
Thanks for the reply Gordon. As for the reason for the combo, we are a Python shop, we are using ActiveMQ for our broker, and we've decided to use amqp1.0 to communicate with ActiveMQ. To that end it looks like using Apache Qpid is the way to go. Furthermore, I would like to use the Qpid messaging API as I find synchronous apps easier to test and its examples mesh with my understanding of how AMQP works (connections, sessions, etc.), and as stated earlier the Python bindings for the messaging API currently don't support amqp1.0 hence going the C++ Python binding route. I may switch to the Proton (reactor) API in the future though. Gordon Sim wrote > It sounds like your c++ client library was built without 1.0 support > enabled. You are probably right about the Ubuntu packages I installed as I have no idea what options they were built with. Gordon Sim wrote > If you build qpid-cpp with proton installed, you should get 1.0 support. I did go ahead and build the packages manually (both qpid-proton so that amqp1.0 support would be available as you mentioned and qpid-cpp), and things are now working for me. Thanks again! -- View this message in context: http://qpid.2158936.n2.nabble.com/Python-qpid-messaging-api-and-amqp1-0-support-tp7661439p7661442.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
