Background thread todo (was Re: Converting tests to JUnit)

Hi, Myrna, et. al.  I apologize for the confusing subject header.  I had 
originally thought seriously about converting the tests to JUnit, but 
realized this was more than I could/should bite off right away.  So I 
changed my mind and changed the text of my message but NOT the subject 
header (oops!).

If you look at the actual text of the message, I'm talking about working 
on the background thread problem that is on the todo list.  I do think 
that the JUnit conversion is very important, but I think it's a bigger 
project than I can take on at this time.  If others are willing to work 
with me on this, I'd be willing to reconsider.

David

myrna wrote:

> David Van Couvering wrote:
>
> > I noticed on the todo list there is a need to have more than one 
> > background thread to enable better scalability with lots of client 
> > connections.  I'm trying to find a way to gently work my way into 
> > doing some work on Derby, and this seemed like a project of small 
> > enough scope to get my feet wet.  Is there any background on this, or 
> > should I just jump right in?  I didn't see any discussion of this on 
> > the list...
> >
> > Thanks,
> >
> > David
> I'd say jump right in!
> There's been some discussion about converting the functionTests to 
> JUnit, and Dan did some work:
> http://mail-archives.eu.apache.org/mod_mbox/db-derby-dev/200503.mbox/%3c42262499.1030004-elHr7NBI3VpYzD5mSbZInQ@xxxxxxxxxxxxxxxx%3e 
>
>
> Then, there's the multi-threaded test in the current functionTests 
> that you might/might not be interested in, see the source in           
> <trunk>/java/testing/org/apache/derbyTesting/functionTests/multi/stress/*
> and
>    
> <trunk>/java/testing/org/apache/derbyTesting/functionTests/harness/MultiTest.java 
>
>
> Myrna