On Fri, 04 Aug 2000, Scott G. Miller wrote: <> > Ah, I believe your right. The solution is to not use a BlockingQueue, but > rather a BlockingStack. That way reclaimed threads get used in preference > over new threads.
Speaking of this, I keep forgeting to ask, should I go to the ThreadPool thing to get threads that are started within the message handeling? It seems a little unnecessary that we have this advanced thread handler so as to recycle threads, but each transfer starts and ends two new Conduit threads. The problem is of course that the node if more or less comitted to running these threads, it can't fail or lock if all threads are in use. <> > Thats due to the fact that the JVM is using native threads, which are == > to Linux processes but with a shared VM context. Annoying in PS, but > perfectly normal. I think most JVMs can use internal threads if you ask them (not that I know how). > > By the way I still would like the recode the thread package :-) > > > And I still don't think its necessary. :) If he really wants to code so bad I'm sure we can find something for him. > > Scott > > ---------------------------------------- Content-Type: application/pgp-signature; name="unnamed" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- -- \oskar _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
