What I imagine is some capability of the script to track where it left off, as a result of say lost network connection.
And when the script is run again it will continue doing whatever it was doing when it was interrupted.
The script has to maintain some kind of "savepoints", I guess, to be able to resume execution from a sane state.
So in addition to knowing where in the script we were, we have to know about open files, file pointers, variables...
While this all sound a bit complex, I have in fact implemented a very simple version of this idea. When the program is terminated in a controlled way (in my case by setting an event) it can manage a restart from that point later.
But I would like to work more on this.
And I am now looking for pointers to techniques for dealing with this issue.
Thanks in advance for all suggestions,
L
In reply to Crash immunity by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |