cvs: phpdoc /en/reference/outcontrol/functions flush.xml

derick Mon Jun 16 14:47:46 2003 EDT Modified files: /phpdoc/en/reference/outcontrol/functions flush.xml Log: - The whole page as a note doesn't make sense... Index: phpdoc/en/reference/outcontrol/functions/flush.xml diff -u phpdoc/en/reference/outcontrol/functions/flush.xml:1.2 phpdoc/en/reference/outcontrol/functions/flush.xml:1.3 --- phpdoc/en/reference/outcontrol/functions/flush.xml:1.2 Wed Apr 17 02:42:33 2002 +++ phpdoc/en/reference/outcontrol/functions/flush.xml Mon Jun 16 14:47:45 2003 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.2 $ --> +<!-- $Revision: 1.3 $ --> <!-- splitted from ./en/functions/outcontrol.xml, last change in rev 1.1 --> <refentry id="function.flush"> <refnamediv> @@ -17,36 +17,34 @@ using (CGI, a web server, etc). This effectively tries to push all the output so far to the user's browser. </simpara> - <note> - <para> - <function>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> - Server modules for Apache like mod_gzip may do buffering of their own - that will cause <function>flush</function> to not result in data being - sent immediately to the client. - </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> - <para> - Some versions of Microsoft Internet Explorer will only start to display - the page after they have received 256 bytes of output, so you may need to - send extra whitespace before flushing to get those browsers to display the - page. - </para> - </note> + <para> + <function>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> + Server modules for Apache like mod_gzip may do buffering of their own + that will cause <function>flush</function> to not result in data being + sent immediately to the client. + </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> + <para> + Some versions of Microsoft Internet Explorer will only start to display + the page after they have received 256 bytes of output, so you may need to + send extra whitespace before flushing to get those browsers to display the + page. + </para> </refsect1> </refentry>