I know. The Doug Lea package is absolutely incredible. Yes, the future result may not be the best thing here. I have a nice thread pool admin package for configuring pools in props files and through an admin jsp. . . .
Aaron > -----Original Message----- > From: Travis Savo [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 20, 2004 7:39 PM > To: 'Turbine JCS Developers List' > Subject: RE: CachingWorker > > >Have you looked at the FutureResult in Doug Lea's util concurrent > >package. It may be useful here. > > I have now, and as usual I'm absolutely blown away by the usefulness of > the > concurrent package. Every time I look a little deeper into it, I > inevitably > find something that would have/will make my life simpler. > > My only concern is that (and this is just an educated guess on my part) > FutureResult will spawn a Thread (which will get joined before the result > will return), which may not be desirable in this particular instance. > > Regardless, it's worth looking into. Perhaps an AsynchronusCachingWorker > might be in order as well... (Eeek, what a horrific name for that! I'll > try > and think of a better one...) > > -Travis Savo <[EMAIL PROTECTED]> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
