I know there is sort of a thread about apache 2 right now, but.... in my experience Mason 1.32 works GREAT with apache 2 / mod_perl 2.  I have been running it for ages.

However, today I noticed that when I am using a custom handler module, flush_buffer does not seem to, well,  flush.  I could provide all sorts of example code, but before I saturate you all with that... is there some invocation trick I need to do to ensure that an apache handler object will correctly flush when flush_buffer is called?  Here's what I am doing now:

# Create Mason objects
#
my $ah = new HTML::Mason::ApacheHandler (args_method => "CGI",
              comp_root=> "/some/path",
              error_mode=>'fatal',
              error_format => 'text',
              data_dir=> "/some/data/path");


Then, down in some component somewhere in my tree, doing:

$m->print("<p>Here is a test of flushing output.  will sleep for 10 seconds.</p>");
$m->flush_buffer() ;
sleep 10;

and I do not see that output...  Now of course there are myriad autohandlers in the way and some fliter methods, but.... shouldn't this just work?  Please tell me I am missing something stupid?

--
--
Shane McCarron
[EMAIL PROTECTED]

Reply via email to