You are talking about a stage queue. Something like journalling filesystems do. Stage Queuing needs to be tuned to the individual app. I did this once for signup data at an ISP. The CGI wrote a file in a queue directory and then tried to go send the request. If it succeeded, it wiped the file. A cron job swept thru every minute and looked for files who were older than 5 minutes, killed their cgi and tried it itself. Any file older than 1 minute with no cgi got tried too.
It's a royal pain in the butt and you have to do all kinds of forward and back checks to make sure you don't flood yourself with duplicates, lose important data and more. Worse, your front line interaction system needs to understand all of that and sniff what stage it's at if the user disconnects and comes back.
And after all that; it maybe fixed two customers automatically in 6 months. You need this almost never. =) It better be real improtant or it just ain't worth it.
--
$you = new YOU;
honk() if $you->love(perl)
In reply to Re: Mechanisms for Fault-Tolerant Perl Scripting
by extremely
in thread Mechanisms for Fault-Tolerant Perl Scripting
by princepawn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |