Re: What you get is what you want

Quartz wrote:
> A stage wrapper start/stop relates to the fact that a TM is running it somehow. (1 or more thread
> involved and calling handleEvent)
> 
> A stage wrapper init/destroy relates to the signal to a handler that its config is ready and
> handler officially exists (wheter they are stateful handlers or not)
> 
> 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?

> This gives the invaluable opportunity to stop a stage, destroy it, while keeping data in its queue
> (lossless), mutate the ss cfg and init the stage again with new parameterization, and start it.

I don't see where and when the load/unload step is called.

Finally, it seems a good idea to add method start and stop to 
StageWrapperIF and create a MutableSandstormConfigIF interface.

Thanks,
Jean M


-------------------------------------------------------
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/