Second, if the information you send has a positional aspect (as in, the HTTP headers must precede the content). If the potential exists that an error message may go out before the full headers, you may disable buffering.

This actually brings us to another caveat: Don't mix buffered and unbuffered output. If your script writes to STDOUT and STDERR, and both of these somehow find their way through the network connection, note that STDOUT is buffered by default but STDERR is not. This is why you'll occasionally see "errors" appear before the actual output. The output is being mixed and naturally buffered output will appear later.

In reply to Re: Re: When to use Autoflush by Fastolfe
in thread When to use Autoflush by chorg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.