> -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED]] > Sent: Saturday, January 12, 2002 11:24 PM > > On Sat, 12 Jan 2002 15:11, Paulo Gaspar wrote: > > > > Why do you insist my CM is a Context? > > > > > > Because you describe it in the same way that I describe Context ? ;) > > > > Let me repeat this bit: > > > > A Context does not allow me to get a SingleThreaded > component and then > > > > release it. Even from an interface POV something is missing. > > > > Do you return components to Contexts? > > Is a Context usually so active as a CM? > > Its possible ;) > > It most cases Context will be sub-classed for a particular domain. For > instance in phoenix there is BlockContext while in ant there is > TaskContext. > Both subclass Context to supply domain specific interaction. You could do > that in your framework ;)
Then the ServiceManager and the ComponentManager could as well be implemented by subclassing a Context and they could be considered Contexts to!!! (Same stretching logic.) > -- > Cheers, > > Pete > > ---------------------------------- > Ancient Go proverb: "Only amateurs > try to come up with 'fancy' moves" > ---------------------------------- I only plaid Go twice. Not enough even to know what fancy is. Have fun, Paulo Gaspar -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
