One comment - as I understand it, the Linux brokers support both federation and clustering, while the Windows broker supports only federation, as qpid clustering relies on OpenAIS, for which there are no publicly available Windows ports.
On Wed, Feb 10, 2010 at 9:17 AM, Kim van der Riet <kim.vdr...@redhat.com>wrote: > Folks, > > I have created a page containing a 0.6 feature matrix here: > http://cwiki.apache.org/confluence/display/qpid/0.6+Feature+Matrix > > It is not directly connected to any of our documentation pages (yet). I > hope to key off this (and related pages) a test coverage matrix which > will give us some idea of what we have covered and what is still > untested. > > What I hope for from the community: > ----------------------------------- > > * Layout ideas - there are may ways to lay out such a matrix, but we > need one that is easy to see and navigate, and presents the information > in a succinct and readily understandable format. > > * List of features - The current list is somewhat arbitrary; I put them > into the list as they came into my head. We need a consistent list of > features that is as far as possible common across all implementations, > not too detailed or fine-grained. The categorization is also somewhat > inconsistent, so ideas here would also help. > > * Content of matrix - matrix needs to be filled out completely, but I > don't know the capabilities of the various implementations well enough > to do it for all. Every cell needs to have *something* in it - if a cell > is blank, it means no-one has supplied a code. > > * Feature descriptions - Each feature should have a link to a detailed > description of that feature. Where there are differences across > implementations, each implementation may either make a distinction or > there may be a separate description for each implementation, but in a > consistent manner. (I have one link in place - it is also to a > non-existent page, but I don't have the syntax for a wiki link right > yet). Can we link to an existing feature description somewhere in our > docs? > > Issues to be aware of: > ---------------------- > > * This table simply states that a feature is available on an > implementation. In the case of clients, the feature is supported against > its matching broker (in the case of Java and C++ - what about > Python/Ruby/WCF?). > > * Interoperability between implementations is not implied here. I have > created an Interoperability page too > (http://cwiki.apache.org/confluence/display/qpid/0.6+Interoperability > +Matrix). > > * HTML - I was unable to get the {table}..{table} syntax to work. So I > have done this using html: > {html} > <table> > ... > </table> > {html} > which is less than ideal from a maintenance point-of-view, but I do have > the HTML portion saved as a file which could be hosted somewhere... > > * Scripting languages and Java are available on most OSs, so I have > simply used "*" to indicate "any". This may be too broad an assumption, > since we have in practice not tested many of the other common platforms > (eg BSD, MacOS, others?) Do we need to break out individual platforms? > > * Because this is effectively a 0.6 snapshot, we will need to compile > something similar for 0.8 and other future releases. How do we manage > this? > > Thanks for looking at this, and please comment and/or add content. If it > makes life easier, I am willing to accept additional content from those > in the know and insert it into the matrix. > > Kim > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
