avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen McConnell <mcconn...@osm.net>
Subject Re: [VOTE] New name for Version 5 ComponentManager
Date Thu, 13 Jun 2002 16:45:21 GMT


Fredrik Hultin wrote:

>I have a question as a newbie user of Avalon.
>Even though ComponentManager maybe is not the *perfect* name for what
>you want to achieve it is still used by all users of the Avalon
>framework isn't it? So why not keep the name so old users doesn't have
>to relearn or read the developer lists to understand what has happened
>to the ComponentManager. As documentation doesn't seem to be you're main
>interest this would probably save a lot of people a lot of grieve...
>
>Imagine sun changing EJB to something else although meaning almost the
>same thing...
>
>I might have misunderstood the reason for the name change and in that
>case please disregard this mail.
>
The reason is that the name "ComponentManager" suggests that an 
implementation of the interface is actually managing the component it 
supplies to the consumer component it is servicing when in fact it is 
simply defining a opaque registry of components accessible by a key.  
The use of the term "Manager" in the interface definition has led to the 
assumption the management functionality "belongs" within a CM 
implementation when in fact the real management should provided by the 
container implementation.

Changing from ComponentManager to ComponentLocator eliminates that 
ambiguity (another wrinkle in the fabric bites the dust).

Cheers, Steve.


-- 

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:mcconnell@osm.net
http://www.osm.net




--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message