At 12:56 AM 6/10/2002 -0400, you wrote:
>Any thoughts or inputs?
Sounds like the notion of Activation / Passivation combined with
persistence mechanisms present in may Application servers.
ie You "activate" object prior to use and then when it is done with for now
you passivate it. ie As things come out of pool they are activated and as
they go back in they are passivated. (Thats taken a little liberty with
explanation but you get the general idea).
For stateful objects in the above frameworks you persist the state prior to
passivating and then reload it prior to coming back alive.
If you are seriously thinking about going down that path I would recomend
you use standard java persistence mechanisms for persisting part.
Before you attempt this I would very veyr very very seriously consider
whether you need it or not.
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
