This sentence about needing to call both ob_flush() and flush() didn't

make much sense.


git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@283315 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Rasmus Lerdorf 2009-07-02 05:40:04 +00:00
parent 3b283caf49
commit fd8f22741a

View file

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.8 $ -->
<!-- $Revision: 1.9 $ -->
<refentry xmlns="http://docbook.org/ns/docbook" xml:id="function.flush">
<refnamediv>
<refname>flush</refname>
@ -13,15 +13,16 @@
<void/>
</methodsynopsis>
<para>
Flushes the output buffers of PHP and whatever backend PHP is using (CGI,
Flushes the write buffers of PHP and whatever backend PHP is using (CGI,
a web server, etc). This effectively tries to push all the output so far
to the user's browser.
</para>
<para>
<function>flush</function> has no effect on the buffering scheme of your
web server or the browser on the client side.
Thus you need to call both <function>ob_flush</function> and
<function>flush</function> to flush the output buffers.
web server nor the browser on the client side. And it also doesn't affect
PHP's userspace output buffering mechanism. This means you will have to
call both <function>ob_flush</function> and <function>flush</function> to
flush the ob output buffers.
</para>
<para>
Several servers, especially on Win32, will still buffer the output from