On 07/08/2012 04:19 PM, Zhihua Che wrote:
What do you mean by 'not supported'? You mean they are not maintained any more?
There is unlikely to be any new development on the qpid::client API. Fixing bugs is a separate question, but would be driven as with all things from prioritisation based on severity of issue, existence of workaround or replacement etc.
I'm wondering the what relations are between qpid::client and qpid::messing. I thought qpid::client is a low-level api which qpid::messaging depends on. According what you said, you mean qpid::messaging substitutes the qpid::client?
Both in fact! It is true that the 0-10 implementation of qpid::messaging re-uses a lot of the underlying qpid::client API. That however was for convenience and time-saving rather than an explicit goal. The qpid::messaging API was however intended as a *replacement* of the qpid::client API - a simpler and richer basis for users to build applications with, and a better foundation for future development of the library.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
