On 04/27/2011 12:11 AM, David Hawthorne wrote:
Ah, I didn't realize the messaging API was for the 1-0r0 spec, I thought it was for 0-10. Thanks for clearing that up, and everything else as well!
The current implementation of the messaging API uses AMQP 0-10. A 1.0 version will be coming along soon.
That said, I for one would be very happy if you could just implement a qpid::messaging API for the 0-10 spec, or give me some way with the qpid::client API to deal with the connection, queues, and receivers procedurally (hopefully supporting a getMessage-like timeout) without having to extend a MessageListener class and without having to deal with SubscriptionManager.
SubscriptionManager was one of the things we wanted to simplify in creating the messaging API. In general I do think that it covers a lot of cases for 0-10 very simply.
There are certainly areas where more work on the addressing is needed. We really appreciate feedback on those cases that are awkward.
If there's a way to do that today, please let me know and document it somewhere. I gave up trying to figure it out after trolling the source. P.S. I am very happy to continue running an 0-10 broker for the long-term forseeable future while the AMQP working group finalizes 1-0 and while vendors break it in. Please don't rush to implement 1-0r0 on my account. :p
Understood!
PPS. I'm kind of curious, are you grafting the 1-0r0 API on top of an 0-10 implementation, or is the C++ broker now implementing both versions?
The API is currently implemented on top of 0-10. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
