File: flush.xml

package info (click to toggle)
php-doc 20100521-2
  • links: PTS, VCS
  • area: main
  • in suites: squeeze, wheezy
  • size: 59,992 kB
  • ctags: 4,085
  • sloc: xml: 796,833; php: 21,338; cpp: 500; sh: 117; makefile: 58; awk: 28
file content (80 lines) | stat: -rw-r--r-- 2,534 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision: 297028 $ -->
<refentry xmlns="http://docbook.org/ns/docbook" xml:id="function.flush">
 <refnamediv>
  <refname>flush</refname>
  <refpurpose>Flush the output buffer</refpurpose>
 </refnamediv>
 
 <refsect1 role="description">
  &reftitle.description;
  <methodsynopsis>
   <type>void</type><methodname>flush</methodname>
   <void/>
  </methodsynopsis>
  <para>
   Flushes the write buffers of PHP and whatever backend PHP is using (CGI,
   a web server, etc).  This attempts to push current output all the way to
   the browser with a few caveats.
  </para>
  <para>
   <function>flush</function> may not be able to override the buffering scheme
   of your web server and it has no effect on any client-side buffering in the
   browser.  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 if you are using
   those.
  </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>

 <refsect1 role="returnvalues">
  &reftitle.returnvalues;
  <para>
   &return.void;
  </para>
 </refsect1>

</refentry>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"~/.phpdoc/manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->