avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen McConnell <mcconn...@osm.net>
Subject Re: Fortres: async/sync init
Date Thu, 18 Jul 2002 17:50:07 GMT


Surely this has to be an attribute of the component profile.  
You may want some component to be lauched immediately and others only on 
demand.
Steve.


Marcus Crafter wrote:

>On Tue, Jul 16, 2002 at 10:56:27AM -0400, Berin Loritsch wrote:
>  
>
>>Setting the CommandQueue to be null is not obvious enough.  What we
>>need is the ability to explicitly turn it on and off.  Most likely
>>through a config parameter:
>>
>><fortress init-policy="lazy"/>
>><fortress init-policy="async"/>
>>
>>Or something along those lines.
>>    
>>
>
>	Ok. Where should we specify such a line ? in the roles file on the
>	root element ? per component along with the handler definition ?
>	or in the xconf file with the handler definition ?
>	
>	Thoughts ?
>	
>	Cheers,
>	
>	Marcus
>	
>
>  
>

-- 

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