You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Ilya Kazakevich <ka...@devexperts.com> on 2009/04/24 11:53:19 UTC
GZIP: pjl-comp-filter vs build-in compression engine
Hello.
Http connector is able to compress data ("compress" param), right?
So, why filters like pjl-comp-filter exist?
Did anybody compare them? Any benchmarks or pitfalls?
I am asking because some people in our company uses pjl, and I do not
understand why do I need some third-party solution, if from-the-box
functionality exists.
What do you think?
Thanks.
====================
Kazakevich Ilya,
MCP, SCJP
====================
Re: GZIP: pjl-comp-filter vs build-in compression engine
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ilya,
On 4/24/2009 5:53 AM, Ilya Kazakevich wrote:
> Http connector is able to compress data ("compress" param), right?
> So, why filters like pjl-comp-filter exist?
I can think of two reasons:
1. At one point, the gzip capability in Tomcat didn't exist (?)
2. It's easier to configure a compression filter that isn't
tied to a servlet container ONCE rather than having to rely
on a different setup if you migrate between containers.
> I am asking because some people in our company uses pjl, and I do not
> understand why do I need some third-party solution, if from-the-box
> functionality exists.
Why not ask those people why they use that third-party library?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAknxylkACgkQ9CaO5/Lv0PAncgCeMNt7zDiC5Dr1QITsHRc2guME
jdoAoKBVoGkB3TsEWTF7+tWx7JFAu2r7
=D3Jr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org