avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leo Sutic" <leo.su...@inspireinfrastructure.com>
Subject RE: Fresh Outlook: (was RE: [desperate plea] RE: The need for 'hints')
Date Tue, 25 Jun 2002 19:52:55 GMT
Robert,

we all agree.

Is this something like what you seek:

  http://marc.theaimsgroup.com/?l=avalon-dev&m=102476881915187&w=2

/LS

> -----Original Message-----
> From: Robert Mouat [mailto:robert@mouat.net] 
> Sent: den 25 juni 2002 21:39
> To: Avalon Developers List
> Subject: Re: Fresh Outlook: (was RE: [desperate plea] RE: The 
> need for 'hints')
> 
> 
> Robert Mouat wrote:
> 
> > <rant subject="Assembler as God">
> <snip/>
> > </rant>
> 
> trying to pull something constructive from my previous rant...
> 
> Things I'd like:
> 
>  1. the ability for the same implementation class to be used 
> as more than one component (e.g. with different configuration).
> 
>  2. the piece of mind to be able to write a component and not 
> worry about name space clashes when looking up roles -- 
> allowing me use generic role names -- or in the case of (1) 
> above - where it is likely that different components from the 
> same class will request the same role, but should be given 
> different components.
> 
>  3. The ability to request role names passed in with the 
> configuration - trusting that the assembler has control of 
> both the configuration and the lookup (so can match the role 
> name with the appropiate component).
> 
> 
> Item 3 could be done using hints (but probably not 2).
> 
> However 1, 2 and 3 could be achieved if the assembler is 
> given the ability to define a mapping of role names to 
> components for each client.  So I'd like to suggest that this 
> ability be part of the framework - i.e. state that containers 
> should give assemblers this ability (so that component 
> writers can feel confident that when writing code that 
> assumes 2 and 3 they are not sacrificing reusuability).
> 
> Something like:
> 
>   "Component writers may assume that a container will give 
> the assembler the ability to specify (uniquely for each 
> client) which component will be returned whenever a role is 
> looked up.  Further a component may receive role names via 
> the configuration."
> 
> 
> Finally I'd also like:
> 
>  4. metadata be optional.  (relying on the assembler if it is 
> missing).
> 
> (but that's mainly because I'm lazy).
> 
> 
> Robert.
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:avalon-dev-help@jakarta.apache.org>
> 
> 


--
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