Berin Loritsch wrote:
>>From: Marcus Crafter [mailto:[EMAIL PROTECTED]]
>>
>>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 ?
>>
>>
>
>Per the container.
>
Disagree.
It is totally reasonable to declar thias at the component profile level.
Why should this be generalized to the container level?
Steve.
>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
