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 a quick fix, I was curious to why it hadn't been done before now?
John On Fri, 01 Apr 2011 11:20 +0100, "Mark Thomas" <ma...@apache.org> wrote: > 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. Adding compression gains very little but adds delay > and increases CPU usage. > > Mark > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
