Hi again... I mean... Peter, > -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED]] > Sent: Saturday, January 12, 2002 2:10 AM > To: Avalon Developers List > Subject: Re: Divergence from Avalon (was Re: [RT] Is Poolable Harmful?) > > > Hi, > > On Sat, 12 Jan 2002 12:14, Paulo Gaspar wrote: > > > Because the string is meant to indicate a Role which in turn > specifies an > > > interface. > > > > Yes, that bit is all over Avalon. > > > > But the String does not make it SAFER. You have to put the right thing > > there. It is not safer than using an Object. It is not like using an > > enumerated type. > > The only reason it is a string rather than a class interface is because > passing in classes could have caused serious issues with ClassLoader and > friends. It also makes it diffifuclt to have multiple types in a role.
Of course. I understood that one. Not a problem in my case if I ever get into loading the whole thing (at the moment I just reload configuration and scripts and it is just fine like this). Anyway, the lack of type safety in both cases remains a fact. > ...snip Delphi sample... > > Actually, I am not 100% sure this works with interfaces but I sure > > used it with classes. > > kool. Yeah! If they ever get garbage collection and a couple of other "details" I go back to Delphi! > > > > I like very much this structure. > > > > > > Its almost there already - except we use different names for it. > > > Context == > > > what you call CM and CM is what you called ServiceManager. > > > > > > The only missing thing is Context passed into ServiceManager > where now we > > > require it to be serialized to a string and tacked ont to end of > > > Role string > > > > Why? > > > > A Context does not allow me to get a SingleThreaded component and then > > release it. Even from an interface POV something is missing. > > > > 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? > -- > Cheers, > > Pete > > --------------------------------------------------------- > Clarke's Third Law: "Any technology distinguishable from > magic is insufficiently advanced". > --------------------------------------------------------- Like... PCs! and other IT stuff. Have fun, Paulo Gaspar -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
