On Thu, 14 Feb 2002 02:08, Berin Loritsch wrote: > >>It also means that we should do the following: > >> > >>* Promote ComponentHandler interface and implementations to Framework > > > > -1 - a concern of the container > > Not necessarily. It is a concern of the Component Developer. A Container > cannot divine that the Component Developer intended when he created the > Component. We had marker interfaces that provided hints--but this is a > tenuous contract. > > We *need* a way to specify how a Container should handle the Component > instances. If a Component is not Threadsafe--which a large number aren't-- > we need to specify a policy for them. Many components can be instantiated > one per thread, but still others must be fully pooled so that a unique > instance is returned *per*request*. > > If we are going to remove lifestyle interfaces, we must have a replacement > mechanism. This mechanism is simple and workable.
Right - but it is container specific. Different containers will use different strategies for implementing this. Some could do it via handlers or factorys, others may specify it via configuration files, others may do it by info objects etc. > > While I would like to see a basic container that leveraged existing > > designs - I don't think it should be in framework that this is done - at > > least not until it is thouroughly specced out and very mature. Keep it in > > excalibur toill then. > > The Container will remain there as long as necessary. I am talking about > the ComponentHandler interface, and a mechanism for the Component developer > to associate their Component with a Handler that will perform correctly for > it. > > If there are N different containers, each with their own unique association > strategy, then we have N different association strategies. The Component > developer will be driven mad! > > This is not good. Perhaps not but we have to come to a conclusion of which strategy to use before we promote one into the framework. -- Cheers, Pete --------------------------------- I think not; therefore I ain't... --------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
