I will make the current extends Thread classes to implement Runnable and then create a thread factory abstraction which will create java.lang.Threads by default. The thread factory could be configured using a system property.
Regards, Rajith On Wed, Nov 19, 2008 at 4:55 PM, Robert Godfrey <[EMAIL PROTECTED]>wrote: > 2008/11/19 Aidan Skinner <[EMAIL PROTECTED]>: > > On Wed, Nov 19, 2008 at 3:33 PM, Rajith Attapattu <[EMAIL PROTECTED]> > wrote: > >> On Wed, Nov 19, 2008 at 9:54 AM, Aidan Skinner <[EMAIL PROTECTED]> > wrote: > > > >>> What strategy did you adopt? It would probably be possible to change > >>> the things that extend Thread to a composite that accept thread, or > >>> implement Runnable. > >>> > >> > >> I haven't really decided on a strategy yet and open to suggestions. > >> Your suggestion also is similar to Gordon which I think is very good. > >> However looking at the code in IOSender/Receiver as well as the > Dispatcher I > >> see they extends the Thread class directly. > > > > I think extending Runnable is probably cleaner, it can just be > > allocated from a threadpool (which could use vanilla, RT or any other > > flavour of thread it desired). I don't see any reason why they have to > > extend Thread directly. > > > > I agree - I think having things implement Runnable is cleaner and more > flexible than extending Thread directly. > > Cheers, > Rob >
