No, not exactly...
No autoflush -> buffered output -> weird performance issues.
Winni
-Original Message-
From: Michael Ludwig [mailto:mil...@gmx.de]
Sent: Thursday, September 09, 2010 8:41 PM
To: modperl@perl.apache.org
Subject: Re: Strange behaviour with Pseudo-Proxy
Winfried Neessen schrieb am 09.09.2010 um 12:39 (+0200):
> After re-reading the mod_perl2 documentation of Apache2::RequestIO I
> figured that I forgot to enable autoflush on STDOUT, which causes the
> $r->print() call to be buffered.
So to sum it up, no autoflush, hence no buffering, hence the p
sen [mailto:nees...@cleverbridge.com]
Sent: Thursday, September 09, 2010 11:22 AM
To: modperl@perl.apache.org
Subject: RE: Strange behaviour with Pseudo-Proxy script
Hi again,
sorry forgot Proxy/Sender.pm in my last mail.
http://dokuleser.privatepaste.com/05e9b4f124/QHvZO0RMoi
Winni
-Origi
-Original Message-
From: Fred Moyer [mailto:f...@redhotpenguin.com]
Sent: Wednesday, September 01, 2010 8:21 PM
To: Winfried Neessen
Cc: modperl@perl.apache.org
Subject: Re: Strange behaviour with Pseudo-Proxy script
Aside from posting the source code so that we can peruse and say "That
Moyer [mailto:f...@redhotpenguin.com]
Sent: Wednesday, September 01, 2010 8:21 PM
To: Winfried Neessen
Cc: modperl@perl.apache.org
Subject: Re: Strange behaviour with Pseudo-Proxy script
Aside from posting the source code so that we can peruse and say "That
might be it", you might try put
Aside from posting the source code so that we can peruse and say "That
might be it", you might try putting a non blocking reverse proxy such
as Perlbal (my favorite, and darn tootin' fast), Nginx, or Varnish in
front of your mod_perl instance so that it does the dirty work of
connection handling an
