Sounds good to me. Perhaps on Scope? What do others think?
Jim
On Jul 14, 2006, at 5:58 PM, Jeremy Boynes wrote:
On Jul 14, 2006, at 2:12 PM, Jim Marino wrote:
What if we said eager init is a component type concept and is
true or false (specified on @Scope)? Then, run level is the SCDL
configuration of eager init. So, a component would be eager
initialized based on the component type info and would be done
so in the order specified by the SCDL runlevel attribute. If no
runlevel attribute were present, we would default it to some
level (maybe 100).
I'm not sure that whether something is eagerly initialized is a
component-type level concept. I don't think that all usages of an
implementation will require that - some may be eager init, some
may not. With that thinking, whether to eager init and with what
priority would be a component level concept.
Eager init may be one of those half-way concepts. In some cases a
dev may want to always eagerly initialize something -e.g.
something that performs some action when a scope comes into
existence. I could probably go either way. When would we have the
case some configurations are eager on others not?
How about we support designation at the component-type level (in
the sidefile or by annotation) that allows the developer to specify
the default level? The presence of a default would imply eager init.
This can be overridden at the component level by specifying a
different level or by allowing eager init to be disabled.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
