Re: What you get is what you want

> > A stage wrapper load/unload relates to its own state.
> > It describes whether the ConfigdataIF proxy
> > (*), queue, controllers, profilables, etc.
> > were built/registered/installed.

 
> By state, I presume that you don't talk about the private fields of the 
> stage?

I talk about the stage wrapper fields that makes the environment/context of operation of a
handler. Although load/unload may not be very usefull, even dangerous for external actors, it
brings continuity and symetry to the stage lifecycle. For any given handler, it is obvious that
all its target sinks must exist before init() gets called. That, to me, clearly declares another
life cycle level: the [un]loaded state.



		
__________________________________ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/