From c32aec004da8fb2a6a5c83b7de1f5702c4362f3a Mon Sep 17 00:00:00 2001
From: Hartmut Holzgraefe <hholzgra@php.net>
Date: Thu, 9 Nov 2000 11:20:54 +0000
Subject: [PATCH] added a note to flush() describing the buffering outside of
 PHP

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@35503 c90b9560-bf6c-de11-be94-00142212c4b1
---
 functions/outcontrol.xml | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/functions/outcontrol.xml b/functions/outcontrol.xml
index d34b45a37b..92de6b680f 100644
--- a/functions/outcontrol.xml
+++ b/functions/outcontrol.xml
@@ -62,6 +62,25 @@ ob_end_flush();
      using (CGI, a web server, etc.)  This effectively tries to push
      all the output so far to the user's browser.
     </simpara>
+		<note>
+		 <para>
+			<fuction>flush()</function> has no effect on the buffering
+			 scheme of your webserver or the browser on the client
+			 side. 
+		 </para>
+		 <para>
+			Several servers, especially on Win32, will still buffer
+			the output from your script until it terminates before
+			transmitting the results to the browser. 
+		 </para>
+		 <para>
+			Even the browser may buffer its input before displaying it. 
+			Netscape, for example, buffers text until it receives an
+			end-of-line or the beginning of a tag, and it won't render
+			tables until the &lt;/table&gt; tag of the outermost table is
+			seen.
+		 </para>
+		</note>
    </refsect1>
   </refentry>