qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carl Trieloff <cctriel...@redhat.com>
Subject Re: new client examples
Date Tue, 19 Dec 2006 22:53:15 GMT

Maybe structure was the wrong word - what I would like to see is that we 
group the same
types of example together across languages - and a queue example in Java 
is also called a
queue example in C# or C++ and shows the same thing in both sets of 
examples. I am not suggesting
that we will have all the same examples, just that we use common 
grouping and names for those
that are the same.

If you look at the API across C++, C# and Java this has been done 
already as far as possible and
Ruby and Python also are very close. I bit of thought will make is a lot 
easier for users of the project - for
example, I want to "consume" from a queue in java - I read the consume 
example. Now I need to do it in .NET, I go
look for the consume example in C#.


Kodichath, Suresh wrote:
> Hi Carl,
> I don't believe we should impose a similar structure on all the
> different languages, but rather allow for various languages to have a
> structure suitable to their own needs. Each of these languages has their
> own requirements / conventions, and therefore I believe that it is best
> suited to follow their own individual semantics. 
> Further we don't follow a similar structure for any of the existing
> code, considering they have their own build environments, testing
> requirements, and so on. Also the level of Qpid features supported
> varies a lot between the various implementations. 
> Considering these I don't think it is useful in putting the effort in
> coming up with a similar (example) structure for all the languages.
> Finally I think it will be preferable to have the discussions here on
> this list.
> Regards,
> Suresh
> -----Original Message-----
> From: Carl Trieloff [mailto:cctrieloff@redhat.com] 
> Sent: Tuesday, December 19, 2006 4:25 PM
> To: qpid-dev@incubator.apache.org
> Subject: Re: new client examples
> I think though should also be given so that we can lay examples down for
> all the clients in a similar structure
> so that someone can look and Java , or C++ or Python and know what to 
> expect if they have already looked at one
> language.
> I thus think we should have some discussion of how we actually want to 
> lay the examples out.
> carl.
> Das, Kapali Tejeswar wrote:
>> +1 from me.
>> Regards
>> Tejeswar
>> -----Original Message-----
>> From: Kodichath, Suresh [mailto:Suresh.Kodichath@iona.com] 
>> Sent: Monday, December 18, 2006 4:05 PM
>> To: qpid-dev@incubator.apache.org
>> Subject: RE: new client examples
>> Hi,
>> I want to propose the following on this, considering the requirements
>> that were raised earlier here. 
>> The requirements are to have the examples compiled as a jar file in a
>> distribution(examples.jar), and also to have examples in source form
> in
>> the distribution under $QPID_HOME/examples.
>> The proposal:
>> 1. Create a new examples directory under trunk/qpid/java as
>> trunk/qpid/java/examples. This will contain samples as in
>> trunk/qpid/java/examples/org/apache/qpid/...  
>> Currently, I think, examples directory has to be under the top-level
>> java directory in-order to be able to create an examples.jar
> consisting
>> of the compiled example classes. 
>> 2. Move /add samples to the relevant directories under java/examples.
>> 3. Create distribution targets for examples.jar, and
> $QPID_HOME/examples
>> in a binary distribution.
>> 4. Create distribution targets for $QPID_HOME/examples in the source
>> distribution.
>> Please let me know if your feedback(s) on this proposal. 
>> TIA,
>> Suresh

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message