> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] > > Berin Loritsch wrote: > > So far most of the attention is for the ComponentLocator name. > > Yes, I agree. > > But there is one thing I don't understand: > I thought we got rid of the Component marker interface, and > so I assumed > that we would be using-recommending the Service interfaces. > So I assumed we would have a ServiceLocator. > > :-?
It seems as if tradition may win out on this. Back when we had ServiceManager/SeviceSelector added to Avalon, we were forced to use another name because the component one was taken. Since we do claim to be a component framework, and not a services framework I think it would be wise to stick with ComponentLocator. Otherwise we will see competition in the minds of pointy-haired bosses who think we are trying to take over the role of .NET or web services. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
