I faced this problem as well and here's what I ended up doing:

sub irregular_run_mode { my $app = shift; $app->header_type("none"); $| = 1; print $app->query()->header(); # code here return ""; }

Yeah. It tends not to work too well if you use cgiapp_postrun to alter the output. Of course, you can fix that with:

sub cgiapp_postrun { my ($app,$outref) = @_; return $outref if $app->get_current_runmode() eq "irregular_run_mode +"; # ... }

Note: I consider this to a be a hack and rather ugly. Please leave comments so if someone wishes to alter the irregular_run_mode so it works normally they will know that they need to alter cgiapp_postrun as well.

antirice    
The first rule of Perl club is - use Perl
The
ith rule of Perl club is - follow rule i - 1 for i > 1


In reply to Re: CGI::Application... flushing output to browser? by antirice
in thread CGI::Application... flushing output to browser? by jfroebe

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.