Hi there,
On Thu, 10 Feb 2000, Ed Loehr wrote:
Fairly certain it's waiting there. I cut my debug timestamps out for
ease on your eyes in my earlier post, but here's one output (of many
like it) when I had the print sandwiched...
Thu Feb 10 14:41:59.053 2000 [v1.3.7.1 2227:1 ed:1] INFO :
Any ideas on why would this output statement takes 15-20 seconds to
send a 120kb page to a browser on the same host?
sub send_it {
my ($r, $data) = @_;
$| = 1; # Don't buffer anything...send it asap...
$r-print( $data );
}
modperl 1.21, apache/modssl 1.3.9-2.4.9...lightly
Ken Williams wrote:
Are you sure it's waiting? You might try debug timestamps before after the
$r-print(). You might also be interested in the send_fd() method if the data
are in a file.
Fairly certain it's waiting there. I cut my debug timestamps out for
ease on your eyes in my earlier
What context is this in? Are you using anything like Embperl, Mason, etc. that
might buffer the entire output in order to find the content-length?
Any difference if you change it to print() instead of $r-print(), or if you
break it into lines and print each line?
Actually, I bet that last
