Real-time updating of php output using flush() in all browsers

Heyy guys,

These days, i'm kinda into hot stuff each day but kinda not having time to document all those. So here i got a little time, let's skip the bla bla.

What exactly is real-time updating means?

Have you ever seen how php output is shown on the browser? No matter what length code or how many loops you put into, the browser always wait to get EVERYTHING, every tiny thing from php output before showing it to the user. Now this isnt convinient eh?

Let's take a scenario where you have to get 1000 records from a database and do very high time consuming calculations on each record. So under normal conditions the user will be looking at a blank page for several minutes [or hours depending on your processor :D ]. This isnt any fault of php, of course if you run php from the terminal (WAMP users dont look confused now) you'll see the output in realtime. So what's preventing it?

 BUFFERING

The Quickie Solve

Just like every other problem there's the easy short code to do this.
Tested with Chrome and Firefox in a standard LAMP server without any server config changes

Usual php output code

1. echo "add this";
2. sleep(5);
3. echo "Program Output";

output [the whole thing displays after 5 seconds]

1. add thisProgram output

php with buffering off

1. echo "add this";
3. echo str_pad("",1024," "); //BROWSER TWEAKS
4. echo " <br />" //BROWSER TWEAKS
6. //telling php to show the stuff as soon as echo is done
7. ob_flush();
8. flush();
10. //just a usual sleep
11. sleep(5);        
13. //second echo statement
14. echo "Program Output";
16. ob_flush();
17. flush();

output [the whole thing displays after 5 seconds]

1. add this
   [waiting 5 seconds]
   Program output

So let's talk about buffering. The feature-thingy that put the whole output at last is because there are several layers of buffering undergoing on the php output to make the output process efficient

1) by php       : the ob_* functions are related to this, ob_flush() would stop/flush the buffer

2) by server    : gzip compression, output_buffering in php5.ini does these

3) by client     : browsers like to do less work, so they wait for considerable about of data to come before showing them to the user

Important tweaks of the code

1) echo str_pad("",1024," "); //BROWSER TWEAKS

As i mentioned browsers do their own buffering to wait for some amount of data before showing content to user

FF        - 512 bytes

chrome - 1024 bytes

IE         - why would you ask? :D

What above code does is adding 1024 blanks to the output, just to make it complete

2) echo " <br />" //BROWSER TWEAKS

Even after above tweak i found that Chrome doesn't show the output as expected. After few more hours of trial and error [at the workplace] I found that it need to read a newline before actually giving any output. Strange huh? So i simply added a html newline and VIOLA :D

Now the code seems working but only buffering (1) and (3) seem to be addressed. So lets make the code complete in a case the server had some bad-ass buffering and caching going. But you wont need all of these, just do trial and error to find the best methods for you.

1. // Turn off output buffering
2. ini_set('output_buffering', 'off');
3. // Turn off PHP output compression
4. ini_set('zlib.output_compression', false);
5.          
6. //Flush (send) the output buffer and turn off output buffering
7. while (@ob_end_flush());
8.          
9. // Implicitly flush the buffer(s)
10. ini_set('implicit_flush', true);
11. ob_implicit_flush(true);
13. echo "add this";
15. echo str_pad("",1024," ");
16. echo "<br />";
18. ob_flush();
19. flush();
21. sleep(5);        
23. echo "Program Output";
24. ob_flush();
25. flush();

References

1) ob_flush()

2) flush()