Absolutely. On 13/06/07, Jonathan Robie <[EMAIL PROTECTED]> wrote:
I like the directions Rajith proposes. Rupert - I think you are basically saying that the new client needs to pass existing tests and future tests (based on JIRAS for M2), and needs to pass existing requirements for the Java client, right? And that you'd like to make sure this is the case before the refactored code becomes the working branch? Jonathan Rupert Smith wrote: > Please add: > > 0. Ensure the existing client unit test suite, sys tests, integration > tests > and performance tests, runs against the refactored client code before the > existing client code is 'broken'. > If necessary/possible convert some tests that use the existing Java > AMQP API > to run through the JMS API. > > 0.5. Identify any JIRAs for M2 that it would be sensible to write > tests for, > and make sure tests for them exist for M2 and the new client code. > > 0.9. Ensure that any existing requirements for the current client code > are > going to be carried forward to the refactoring. At the moment, I can > think > of: > - Ensure retrotranslation to Java 1.4 will work. > > On 13/06/07, Rajith Attapattu <[EMAIL PROTECTED]> wrote: >> >> 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 >> >
