Berin Loritsch wrote:
>>From: Stephen McConnell [mailto:[EMAIL PROTECTED]]
>>
>>Berin Loritsch wrote:
>>
>>
>>
>>>>From: Marcus Crafter [mailto:[EMAIL PROTECTED]]
>>>>
>>>>
>>>> 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.
>>
>>
>
>How would you handle this sort of thing in Merlin? It is something
>that you would find in the component descriptor, or in the
>configuration.
>Right now, we have it set up so that the decision for async
>initialization
>is done per component. However, it is easy enough to change to per
>component. I would still advocate the attribute to be applied to the
>container as a default if no init policy is selected on the
>per-component
>level.
>
The current Merlin 2 approach is to instantiate the chain of components
during kernel startup. However, the architecture (and first release)
will ensure defferred object activation (until a lookup request is
invoked by a client on a CM/SM) - but this doesn't make sense for
components that you want up-and-running as servers. To resolve this
some attribute is needed on a profile (the component declaration in the
container config). But that's more of a ACTIVATE_ON_STARTUP
declaration. In Merlin is kind of doesn't make a lot of sence to
declare delayed or immediate activation as a default condition - because
Merlin is sorting out and activating components (that you may not have
included in your config) as part of auto-assembly and the resolution of
dependencies can cross container boundaries. This means that the scope
is not container level but "kernel" - so if any policy were declared I
guess it would be in the kernel definition.
Cheers, Steve.
(who's just thinking out-loud)
>
>
>--
>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]>