if you just want the script to run without dying, but you don't care about
seeing the end-result in the browser you can...
<?
function this_function()
{
// do a bunch of wacky stuff here...
}
?>
or.. if you want to see something in the browser.. you can do something like
this. (This is from actual working code I wrote a long time ago... i
trimmed out the stuff specific to my application but you should get the
idea...)
<?
set_time_limit(0);
session_start();
// the setup...
if (!isset($_SESSION['count'])) {
$_SESSION['count'] = 0;
$_SESSION['chunks'] = array_chunk(file('/some/file.txt), 50);
$_SESSION['start_time'] = date("Y-m-d H:i:s");
$_SESSION['chunk_count'] = count($_SESSION['chunks']);
header('Location: ' . $_SERVER['PHP_SELF']);
exit();
// the run through
} else {
++$_SESSION['count'];
echo 'Start Time: ' . $_SESSION['start_time'] . '<br />';
echo 'Pass: ' . $_SESSION['count'] . ' of ' .
$_SESSION['chunk_count'] . '<br />';
if (isset($_SESSION['chunks'][0])) {
foreach ($_SESSION['chunks'][0] as $k => $v) {
$line = trim($v);
//
// your code to do something with the line goes here.
//
} // END foreach loop
array_shift($_SESSION['chunks']);
echo '<META HTTP-EQUIV="REFRESH" CONTENT="0; url=' .
$_SERVER['PHP_SELF'] . '">';
} else {
// must be done! Display the results.
$_SESSION['end_time'] = date("Y-m-d H:i:s");
echo '<pre>';
print_r($_SESSION);
echo '</pre>';
}
}
?>
"Jerry" <no**@none.com> wrote in message
news:un********************************@4ax.com...
Hi All
I would very much appreciate your help:
I have two scripts alternating in the background triggering themselves
mutually. Here is how:
1.)
Script A does something and then calls Script B through the header()
function. Using something like
header("Location:http//mydomain.com/scriptb.php");
2.)
Script B then does something as well and afterwards calls Script A
again also using the header() function.
After exactly 10 rounds my browser suddenly shows an PHP error message
which mentions a "circular redirection" error aborting the script.
QUESTION:
Is there a way to avoid that error?
PURPOSE:
The two-script-concept was supposed to be a solution to prevent
time-outs during time consuming processes by simply handing the
process over to another script before the time limit is reached thus
initiating a new script session by the other script which would
continue the process. In other words: The process is being kicked back
and forth between the two scripts until it's finished.
Any ideas ???? Thank you guys.
Jerry
