[Stackless] Re: Execution state persistence for workflow application
tismer at tismer.com
Tue Dec 9 05:37:59 CET 2003
Alan Kennedy wrote:
> [Serge Orlov]
>>>The problem is that one day you will
>>>have to upgrade your program and your last dumpexec won't be
>>>compatible with your next loadexec(). You will have to separate
>>>code from data to do it. So it means execution persistence is not
>>>enough for real life use. Why not just use data persistence alone?
> [Paolo Losi]
>>In fact data persistence is not sufficient to stop and resume scripts
>>in case, for example, system reboot.
>>I do want my workflow scripts to resume exactly (and with the same
>>globals/locals setup) where they left...
>>The real alternative would be to define a new script language
>>with standard constructs (for, while,...) but again... i don't want
>>to reinvent the wheel.
>>I do not seen execution persistence as an alternative to data
>>persistence: I would need both.
> You might want to investigate Stackless python, an excellent research
> work which can save and resume execution state, to some degree. Try
> the following google query
Here is a small example that I wrote last weekend for Zope.
It looks very simple, it lets you run 10 answers
*from* the web server against the client in a loop,
with no visible call-backs.
It *is* a server loop, but ti's obvious that there
cannot be a simple loop, since the server freezes
until the next request come in.
Well, it looks simple, but here is the real power!
Will try to finish this and publish, soon -- chris
Christian Tismer :^) <mailto:tismer at tismer.com>
Mission Impossible 5oftware : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34 home +49 30 802 86 56 mobile +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
Stackless mailing list
Stackless at www.tismer.com
More information about the Stackless