Hi Rajith, I'm +1 for most of this.
The only exception (obviously) is the JMS examples for the Java side. These obv need to be specific. I'm posit that for most of our Java users this is what they're most interested in, and that they mainly just want to edit some JNDI stuff and run a script to get started. IIRC my JMS examples did this (more or less). I haven't yet had time to look at the new JMSExamples but will do shortly. Rgds, Marnie On 4/27/08, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > > Hi All, > > Based on all the discussion we had so far I like to propose the following > strategy for creating a common set of examples and a getting started guide > for Qpid. > > a) I propose we have a common set of examples across all the languages. > - Currently we have such a set of examples for java, c++ and python. > These examples are written to demonstrate the capabilities of the standard > AMQP exchanges types. > We can expand this to ruby and .NET when those clients are 0-10 > ready. > - This sends a strong statement about our commitment to AMQP and > interoperability. > - These examples can be checked for interop with the respective builds. > For example c++ build checks it's examples with python. > (I also have a cruisecontrol build that runs all examples against > each > other) > This ensures that all examples stay current and interoperable. > > b) We could then leverage these examples to build a "getting started > guide". > - For starters senaka is planing to add a README file for each example > folder and also a description about how to use the verify scripts > - Jonathan has alluded to (in the other thread) contributing some > documentation which we can use as a basis for a more comprehensive > tutorial. > > All forms of comments and suggestions are most appreciated. > > Regards, > > Rajith Attapattu > Red Hat > http://rajith.2rlabs.com/ >
