On Wed, 11 Sep 2002 08:37, Greg Steuck wrote: > In one of the recent changes you switched excalibur.event to its own > copy of thread pooling. I am a bit lost now because I would like to > use AbstractThreadManager in my otherwise Phoenix application and I > can't really setThreadPool to the pool provided by Cornerstone > ThreadManager (for it's the original excalibur.thread pool) > > What would you recommend me to do? I could have another pool in my app > but that would be ugly.
Hmmm ... I think Berin this because he did not want to couple against the old pooling code that requires Poolable etc. It may be a good idea to cleanup all that code and reduce its coupling to old pool stuff. We can leave compatability layers in there so people can gracefully migrate from it or when mpool does not offer everything we need (like ResourceLimiting pools). We could also fix up those spelling mistakes ;) > P.S. I wonder if it is a speech impediment on my side, but I always > end up typing excalibur as excalibu_t_ the first time :-) err .... :) -- Cheers, Peter Donald *------------------------------------------------* | The student who is never required to do what | | he cannot do never does what he can do. | | - John Stuart Mill | *------------------------------------------------* -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
