Peter Royal wrote:
On Monday, January 27, 2003, at 10:13 PM, Berin Loritsch wrote:
There is a major bug with the Excalibur Thread package that only
affects some systems. I am not sure what the final reason is, but all
the mutex/threadpool complexity created an infinite loop/deadlock
when the thread pool was destroyed.
Adding a ThreadPool enabled ThreadManager is still possible--but
I would prefer that it isn't done at the core level. It is just
too troublesome.
Could Doug's packages become the basis for a new threadpool
implementation? I'm not tied to an implementation, rather I liked the
pluggability across our other components...
-pete
You could, but then again, you don't really need the Excalibur
Thread package with Doug's package either.
The Executor API is fairly flexible, and you have queue implementations,
pool implementations, and immediate executors.
I am trying to simplify things tremendously.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
