Hi Folks, I think we've gotten to the point that we have rough consensus, and it's clear how to move forward.
I think there is broad agreement on the following goals: 1. We should have a low level client API that maps directly to the AMQP protocol across all language implementations. This will make it easier to keep language bindings consistent and to test them. 2. Early adopters can work with the low level client API, with the explicit understanding that this API is likely to change until the protocol stabilizes. 3. The JMS implementation should be built on the Java AMQP client, which will make it easier to keep it consistent with the other language bindings and to test. 4. The existing Java client code needs to be re-factored. The current prototype available has reused and rearranged existing code as much as possible. 5. We should consider how to provide AMQP functionality beyond what JMS offers. Several strategies were explored, including extending JMS and designing the low level AMQP client so that it can be used together with JMS using casting. Based on this, I think we should do the following: 1. Refactor the existing Java client code so that it implements JMS functionality on top of a low level AMQP API. 2. Identify a list of key bug fixes/JMS extensions in the M2 branch,and reflect these in the new Java client code. Unless I hear otherwise, this is the plan I intend to pursue. Rajith
