I think we're also using the built-in components, not the one provided
by Resin 3. Is there really any benefit to not having built-in
compression? The filter has already been written and I doubt it has
changed much in the last year to six months.
-Matt
Matt Raible wrote:
Let's rephrase the question:
For the high-traffic Roller sites, are you using your container to
GZip output, or are you using Roller's built-in GZip filters?
I'm using the built-in filters, not any that are provided by Apache or
Tomcat. Therefore, I'm -1 on this change.
Matt
On 11/10/05, Allen Gilliland <[EMAIL PROTECTED]> wrote:
would anyone be opposed to disabling the Roller gzip filters for default
installs?
to make it easier to toggle on/off i am thinking we can add a config property like
"compressOutput.enabled" and make some small modifications to the
CompressionFilter to check that property before compressing output. that seems better
than forcing people to modify the web.xml file.
this seems appropriate because most containers these days offer their own
compression capabilities which means it's one more thing that we don't have to
manage ourselves. obviously we can leave what we have in place for those users
who still want it, but just have it disabled by default.
this would be for Roller 2.1
-- Allen
