ID: 23877
Comment by: pclark4 at austin dot rr dot com
Reported By: sthomas at townnews dot com
Status: Open
Bug Type: Feature/Change Request
Operating System: Redhat Linux
PHP Version: 4.3.2
New Comment:
when i try and play games or check my mail in yahoo is says brouser
refuses to log in (rejected cookies
Previous Comments:
------------------------------------------------------------------------
[2003-06-30 11:05:43] sthomas at townnews dot com
Implicit flush is turned off in the php.ini file, but that's only the
default status. Calling ob_implicit_flush should enable autoflushing.
The CLI *does* work if I set the output_buffering setting to 0, but
here's the screwy part: Set it to any non-zero value, and flushing
doesn't occur at all.
Setting output_buffering to 1024 would imply that after 1024 characters
are sent to the buffer, the buffer is sent to screen/browser. This is
not the case. So not only is ob_implict_flush completely ignored when
output_buffering is set to a non-zero value, but output_buffering
doesn't flush after the designated value either. At least not with the
CLI.
But don't take my word for it. Set output_buffering to *anything*
above 0, then run this script with the CLI:
<?PHP
ob_start();
ob_implicit_flush(1);
while(1)
{
for ($i = 0; $i < 1024; $i++)
print ".";
flush();
sleep(1);
}
?>
You'll see that no flushing is taking place... at all. Even with an
explicit call to flush(), and even though ob_implicit_flush says that
output buffering should now be disabled. Yes ob_end_flush() works,
however the PHP documentation says ob_implicit_flush does an implied
call to ob_end_flush(). So either the documentation is wrong, or PHP
is broken. If the documentation is wrong, why have ob_implicit_flush
in the first place if it doesn't actually do anything?
Because so far with recent versions of PHP, I haven't been able to
create a single test case where ob_implicit_flush actually did
anything.
------------------------------------------------------------------------
[2003-06-30 09:33:08] [EMAIL PROTECTED]
There's a second level of buffering after the ob_ buffering. What is
your implicit_flush setting? Please also refer to
http://www.php.net/flush
------------------------------------------------------------------------
[2003-06-30 08:02:09] sthomas at townnews dot com
So... did you read the report at all? Did you see the part where I
quoted the PHP documentation? Let me do it again:
"Turning implicit flushing on will disable output buffering, the output
buffers current output will be sent as if ob_end_flush() had been
called."
Therefore, according to this, calling ob_implicit_flush *IMPLIES A CALL
TO OB_END_FLUSH*! What part of YOUR OWN DOCUMENTATION do you not
understand? Either the documentation is wrong, or PHP is wrong.
Whichever it is, fix it so there's at least some consistancy.
------------------------------------------------------------------------
[2003-06-29 21:07:05] [EMAIL PROTECTED]
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php
You should've used ob_end_flush(); instead of ob_implicit_flush();.
------------------------------------------------------------------------
[2003-05-29 15:51:03] sthomas at townnews dot com
Please note that the manual says this:
"Turning implicit flushing on will disable output buffering, the output
buffers current output will be sent as if ob_end_flush() had been
called."
Now, I've set output_buffering = 0 in my php.ini script, so supposedly
ob_implicit_flush will flush any buffers started by the script itself,
and continue flushing output thereafter. Try this:
<?PHP
ob_start();
ob_implicit_flush(1);
while(1)
{
print "Hi!";
sleep(1);
}
?>
This script will not output "Hi!" after each iteration through the
loop. Supposedly the documented behavior of ob_implicit_flush is to
flush all output buffers once it's called, and disable output buffering
for further statements that produce output (print, etc.)
So either the documentation is wrong, or there's a bug in
ob_implicit_flush. You decide.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=23877&edit=1
