On 01/04/2011 11:15, John Baker wrote:
Hello,
The Tomcat AJP Connector does not support compression. Why has this been
ommitted?
Because the link between Tomcat and reverse proxy will nearly always
have significantly more capacity than the link between the client and
the reverse proxy.
Mark,
In general, that's true. However, for high performance applications
measuring results in milliseconds - ie noting that a request with
compression takes 60ms and without takes 120ms - it's an issue. And it
seems so easy to fix by putting compression into the Tomcat AJP
connector. Given it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John,
On 4/1/2011 6:45 AM, John Baker wrote:
In general, that's true. However, for high performance applications
measuring results in milliseconds - ie noting that a request with
compression takes 60ms and without takes 120ms - it's an issue. And
AM
To: Tomcat Users List
Subject: Re: mod_jk / AJP and compression
On 01/04/2011 11:15, John Baker wrote:
Hello,
The Tomcat AJP Connector does not support compression. Why has this been
ommitted?
Because the link between Tomcat and reverse proxy will nearly always
have significantly more
