----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 30, 2001 5:38 PM
Subject: Re: [PATCH][Collections] a variety of new classes...


>
>
> On Sun, 29 Apr 2001, James Strachan wrote:
>
> > I've a variety of collection utility classes that I've used on a various
> > projects that I'd like to contribute to the collections project.
> >
> > I've attached all the source code for the new classes in the
> > org.apache.commons.collections package with ASF licences attached as a
JAR.
> > Its all ready to just unjar into the source directory of the collections
> > project. I haven't included JUnit test scripts for this code yet, I
thought
> > I'd wait for approval of the patch first before porting those.
> >
> > The code consists of new classes together with a patch to
CollectionUtils to
> > add a number of extra helper methods. I've attached a seperate
patchfile.txt
> > which contains the new methods on CollectionUtils.
> >
> > Probably the easiest way to browse the code is to unjar the patch.jar
into
> > the source directory and build the javadoc and browse that. I'll try
give a
> > brief overview of the classes here.
> >
>
> I like the set you are proposing, but have one comment/question.
>
> It seems to me that SynchronizedQueue might fit better into a package of
> classes specifically focused on communicating between threads in a
> multi-thread application.  One such set of classes is my
> "threading" proposal in the sandbox.  Another possible source was
> suggested on the list today (the "util.concurrent" thread).
>
> What would you think about focusing the "collections" package on things
> that are independent of multi-thread communication assumptions, and having
> a separate Commons package ("threading" or "multithread" or whatever) that
> is specifically focused on that need?
>

+1 on separation.

> Craig
>
>

Reply via email to