m3rajk — Fri, 26 Sep 2003 16:12:34 +0000

i'm using LAMP with mozilla and i didn't get ti sent actively. i got it all at once

ROB — Wed, 24 Sep 2003 02:18:41 +0000

i think more specifically some servers override it, not browsers (while some browser may but i've never experienced it), in particular most or all Windows servers. They don't necessarily override it, they just provide their own buffering, so while the php app flushed it's still caught up in the webserver.

m3rajk — Tue, 23 Sep 2003 18:30:08 +0000

it's a set of lines with at the begining of each. i noticed in the write up it says that some browser override it (specifcally ie)

Mark Hensler — Mon, 22 Sep 2003 18:49:27 +0000

If the content your flushing is within certain HTML blocks (like tables), then the content wont be displayed untill the browser sees the end of the block.

m3rajk — Thu, 18 Sep 2003 18:25:36 +0000

i did that so it would update as it moves from table to table. but it still didn't print out actively. went back and read it again. some browsers override flush. not sure if that's why it did that or not. i'm testing the site in mozilla 1.3.1 then making sure the display isn't too far off in ie.

i figure ie is going to be forgotten by the masses before M$ comes out with the new browser, so since i like mozilla that's what all the messages say to use if somethng's brokeni note it was tested in mozilla 1.3.1 and the person browseing should upgrade to the latest stable release of mozilla (i know it's at 1.4.1 but i'm going to upgrade after i complete the site simply so i'll know the site can be handled by 1.3.1 since alot of people i know only upgrade every 2 or 3 changes that aren't marked as security fixes)

Mark Hensler — Thu, 18 Sep 2003 00:54:37 +0000

That would work.

I usually put it at the bottom of the inside of large loops.

m3rajk — Mon, 15 Sep 2003 18:31:47 +0000

ok. so that would mean i need to place it after each sql action? or at the end of all of them? (i want ti to update as it moves through them because it takes a little while since i'm on a p1 (pre-mmx)/166mhz processor)

ie:

<?php
        echo \"      <br />Deleting of user $deluser from table BIO\";
        flush();
        $dfs=mysql_query(\"DELETE FROM bio WHERE uid='$todel'\", $db);
        if(mysql_affected_rows($db)==1){ // successful deletion
          $gone++; echo \"      <br />Removed $deluser (user # $todel) from table BIO\";
        }else{ // error
          $errno=mysql_errno($db); $error=mysql_error($db); $delerr=1;
          $errs.=\"<br />Bio:$errno: $error\";
        }
        echo \"      <br />Deleting of user $deluser from table COMMENTS\";
        flush();
?>

or the end of each of those?

Mark Hensler — Mon, 15 Sep 2003 17:05:18 +0000

flush() only sends whatever output is in the buffer to the client. There's no way it could corrupt your db, or otherwise alter the performance of your script.