There are a few ways of doing this. None is going to be perfect. As already suggested you need to set autoflush. Likewise you need to end each print with a newline, IIRC some browsers will not render a line until a newline is received (or the document closed). Likewise, your status messages cannot be embedded in a table, would usually have to wait for the table to be closed to be able to render properly. And finally I think a browser may disconnect afterawhile if not data is being received, if these processes take too long you'll have to print to keep the connection open (whitespace would be your best bet).

Another means of doing this is server-push, last I checked it was only supported by Netscape though (it uses the multipart/x-mixed-replace MIME-type).

--
perl -pew "s/\b;([mnst])/'$1/g"

In reply to Re: output to screen in real time by belg4mit
in thread output to screen in real time (CGI) by belize

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.