> I'm using it on a regular basis. Here's the config snippet:
>
> Alias /majcd /usr/local/www/cgi/aef/majcd
> <Location /majcd>
> SetHandler "perl-script"
> Options +ExecCGI
> PerlHandler Apache::OutputChain Apache::GzipChain Apache::Registry
> </Limit>
>
> It's really a regular Apache::Registry setup, except for the added
> modules in the PerlHandler line.
Eric, does Apache::GzipChain really work? Do you feel the difference?
Should it be endorsed?
I've this item in the guide but have never tried it myself. Doesn't it
slow down the respond time because it has to compress stuff, I know it
compress the stream as it arrives, but still it's a delay... Does size
matters?
Obviously you want to do some internal buffering or calling print very
infrequently because if you send the output in small chunks the
compression will be quite bad as there will be no enough characters to do
reduce the size.
Can anyone post the benchmarks?
Does anyone have the statistics for a percentage of clients supporting
application/x-gzip MIME type (which this module requires)? Well probably
the correct question is how many browsers set correctly the
Accept-Encoding header and its User-Agent headers.
_______________________________________________________________________
Stas Bekman mailto:sbekman@iname.com http://www.stason.org/stas
Perl,CGI,Apache,Linux,Web,Java,PC http://www.stason.org/stas/TULARC
perl.apache.org modperl.sourcegarden.org perlmonth.com perl.org
single o-> + single o-+ = singlesheaven http://www.singlesheaven.com
>
> Alias /majcd /usr/local/www/cgi/aef/majcd
> <Location /majcd>
> SetHandler "perl-script"
> Options +ExecCGI
> PerlHandler Apache::OutputChain Apache::GzipChain Apache::Registry
> </Limit>
>
> It's really a regular Apache::Registry setup, except for the added
> modules in the PerlHandler line.
Eric, does Apache::GzipChain really work? Do you feel the difference?
Should it be endorsed?
I've this item in the guide but have never tried it myself. Doesn't it
slow down the respond time because it has to compress stuff, I know it
compress the stream as it arrives, but still it's a delay... Does size
matters?
Obviously you want to do some internal buffering or calling print very
infrequently because if you send the output in small chunks the
compression will be quite bad as there will be no enough characters to do
reduce the size.
Can anyone post the benchmarks?
Does anyone have the statistics for a percentage of clients supporting
application/x-gzip MIME type (which this module requires)? Well probably
the correct question is how many browsers set correctly the
Accept-Encoding header and its User-Agent headers.
_______________________________________________________________________
Stas Bekman mailto:sbekman@iname.com http://www.stason.org/stas
Perl,CGI,Apache,Linux,Web,Java,PC http://www.stason.org/stas/TULARC
perl.apache.org modperl.sourcegarden.org perlmonth.com perl.org
single o-> + single o-+ = singlesheaven http://www.singlesheaven.com