> MPool is a very optimized pool with asyncronous Pool size management. > The interfaces are different from the "pool" package. MPool was named > for "Managed Pool". > > The question is: > > Do we make MPool its own package, incorporate it into Pool, or > incorporate it into Fortress. > > I would like it to be used on its own, but it does require Event. > (and more specifically command). > > I see it being able to replace "Pool", but legacy concerns prevent > a clean move.
Without knowing about the code: if it is possible to write a compatibility wrapper around MPool providing the functionality Pool provides, then it should go into the Pool package. If not, it shouldn't. A Pool implementation that requires Event seems to me like it should be logically grouped with Event. OTOH, you might not want the MPool with Event or Command. So it should have a different jar, and hence a different package. right? - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
