RE: Divergence from Avalon (was Re: [RT] Is Poolable Harmful?)

[Leo Sutic]

> From: Paulo Gaspar [mailto:[EMAIL PROTECTED]]
> 
> > If we had non-string roles, configuration would be much harder,
> > I'm afraid.
> 
> Hi Leo,
> 
> I agree with you BUT I am not talking about that.
> 
> I am not talking about changing the type of a Role but about changing 
> the type (and name) of the parameter for ComponentManager.lookup() 
> from:
>   ComponentManager.lookup(String role)
> to:
>   ComponentManager.lookup(Object query)
 
Yes, but the query object sent in must match something in the configuration
of the component manager. That is, for every query object, one must be able 
to specify something in the configuration to guarantee that the query object
results in just that component.

I just see this as making the CM much harder to use - how does the Composable
component know what query to pass to the CM? How does the CM know how to
parse an NDimQuery?

The way I see it, the power of the CM lies in not letting the Composable
specify *too much* what it wants. The more intricate queries you allow the
Composable to send, the more complex is the contract between the Composable
and the CM and the higher the coupling. 

/LS


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>