> -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 09, 2002 9:18 AM > > On Wed, 9 Jan 2002 03:12, Berin Loritsch wrote: > > I think we have come to the conclusion that Poolable interface is not > > helpful, and makes certain things more difficult. The remainder of the > > discussion has been what *else* people have found limiting. If Avalon > > is not to be moved into absolescence, it must learn from its > limitations. > > Periodically we need to discuss what works and what does not work. > > Agreed - lets throw out ComponentSelector and possibly Component > interface > > /me runs and ducks for cover ;) > > -- > Cheers, > > Pete
LOL! Actually I am starting to find the ComponentSelector concept more interesting. But yeah! Kill the Component interface! =:o) However, I am not so sure if it is possible to build a ComponentManager that suites all needs and if it really matters. I mean, the ComponentManager is not the most reusable bit of Avalon and for many projects neither is it the most interesting. I find it more important to make as many parts as possible usable without assuming there will be a component manager. Note: I still love the "life cycle" stuff. Have fun, Paulo Gaspar -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
