Hello, Berin, Leif and All_the_interested! :-)
* component startup order (derived from the dependency graph)
currently has an interesting interference with
* activation policy
In fact, all the components are first sorted topologically,
and then this sorted list is randomly torn into 3 parts:
inline, backbground and lazy activation policies.
In fact if we have dependency
A - > B
but A has inline activation and B - background, A will
still be (probably?) initialized before B.
Lazy initialization worries me somewhat less - I have
a feeling that the component will come up in proper time,
but it looks like if a component with inline initialization
depends on a component with background initialization it
should either be considered an error or the policy for
the offending component should be changed to inline.
Thoughts?
-Anton
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
