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. ...snip Delphi sample... > Actually, I am not 100% sure this works with interfaces but I sure > used it with classes. kool. > > > 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 ? ;) -- Cheers, Pete --------------------------------------------------------- Clarke's Third Law: "Any technology distinguishable from magic is insufficiently advanced". --------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
