On 07/06/07, Robert Godfrey <[EMAIL PROTECTED]> wrote:
In the AMQP working group we have been talking about some sort of standardisation of an AMQP API. If such a standardisation takes place I would expect each Qpid client library to implement to that standard. Before such a standardisation we obviously running a risk by defining our own API that it is not substancially the same as that agreed by the AMQP working group - then we would be having to support three separate APIs :-(
Yes, two APIs is more than enough work in my opinion and three would be an API too far.
My view remains that we should build an internal API based on AMQP in terms of which we write our JMS implementation. I would not be encouraging our users to use that "AMQP" API until such time as AMQP has sufficiently stabilized and established API guidlines.
I agree with this. What is your view on how any AMQP-specific features should be exposed to end users (in Java)? RG
