Also on the subject of interop. The interop spec has been implemented for a number of test cases, and I will soon be adding test cases for all field table types too. Currently it passes on C++, Java and .Net with Java broker for M2.
There were also requirements in that spec for automated testing. In outline, this meant having builds output a broker executable and a test client executable to standardized locations, with start/stop scripts. There would then be a master test scripts that launch all the possible combinations of brokers/test clients in sequence based on what is available at the end of a build and interop test them all and collate the results in a format that automated build systems understand (XML output from JUnit). This has not been attempted yet because so far I have only looked at client interop over the Java broker and am launching the broker and test clients by hand every time. In addition to Rabbit and OpenAMQ I would be interested to run the perftests and interop tests through the Qpid C++ broker. Rupert On 10/01/2008, Rupert Smith <[EMAIL PROTECTED]> wrote: > > So is the plan to move JMS support onto pure 0-9, then revert 0-8 support > to be pure too for interop with other 0-8 brokers? Or will JMS continue to > run over impure 0-8, with purity restored through the STRICT_AMQP flag? > > Rupert > > On 10/01/2008, Robert Godfrey <[EMAIL PROTECTED]> wrote: > > > > Presume that all the Qpid M2 artifacts do (since they interoperate) > > > > -- Rob > > > > On 10/01/2008, Robert Greig <[EMAIL PROTECTED]> wrote: > > > On 10/01/2008, Robert Godfrey < [EMAIL PROTECTED]> wrote: > > > > > > > Since I haven't yet had the time, the broker on M2.1 speaks "pure" > > 0-9 > > > > but "impure" 0-8 > > > > > > How many speak "impure" 0-8? Is that just Qpid java? > > > > > > RG > > > > > > >
