Well, I got curious, and didn't find much in a quick RTFM and STFW, so I hacked these:
#big.php
<?
if (!$_POST['num']) {
$num=(int)1;
}
else {
$num=$_POST['num'];
}
$start=(int)$num;
while ($num<($start+1000000)) {
$num++;
}
echo "<form action=\"big.html\" method=post>";
echo "<br><br>Current value of \$num is:\t $num<br><br>";
var_dump($num);
echo "<br><br><input type=hidden name=num value=".$num.">";
echo "Continue?<br><input type=submit name=submit>";
?>
#bigstring.php
<?
if (!$_POST['st']) {
$st="abcdefg";
}
else {
$st=$_POST['st'];
}
while ($num<1000) {
$st.="abcdefg";
$num++;
}
$length=strlen($st);
echo "<form action=\"bigstring.html\" method=post>";
echo "<br><br>Current length of \$st is:\t $length<br><br>";
var_dump($st);
echo "<br><br><input type=hidden name=st value=".$st.">";
echo "Continue?<br><input type=submit name=submit>";
?>
and then ran the integers to 150 million and the string to 140 thousand chars without any problems...except I got tired of punching the submit button ... and waiting for the downloads when I had var_dump uncommented in the string script... 😉
It seems like the sticking point would be the decision on where to put the info. It couldn't go in a GET, I don't think ... surely you'd overflow the browser's address window. A POST seems to work, but it will require ever increasing amounts of load and post times over the network ... and I imagine if you start doing it with session variables you might fill up your /tmp at some point....
