Ryan et al,
I don't want to start another firestorm of issues. Mod_gzip has and is
working well for Apache 1.x users. It supports both static and dynamic
content and there are even some hacks to support compressed SSL. It's
entirely configurable and you can easily disable problematical browsers.
There is certainly no need to gzip content on the web server. As for
memory leaks, I can't recall ever seeing a bug report about that. It's
carried all over the world so I'm sure someone would have said something
by now. That being said, if someone does find an issue with the core
compression/decompression algorithm I'd like to hear about it. I'm sure
it would be possible to contact Dr. Adler the co-inventor.
Anyway it's public domain and anyone can use it. Whether or not you
include it in the core is not my decision. Is it useful, I think so, but
then so are a ton of other modules. Others at ASF can always decide
whether or not to include or not.
Ian, I'll chat with Kevin on getting you a copy of the code. Although I
think he will want to wait until Apache 2.x goes beta. He's the author
and it's his decision.
Regards,
Peter
-----Original Message-----
From: Ryan Bloom [mailto:[EMAIL PROTECTED]]
Sent: Saturday, September 01, 2001 9:50 PM
To: [EMAIL PROTECTED]; Cliff Woolley
Subject: Re: [PATCH] Add mod_gz to httpd-2.0
On Saturday 01 September 2001 20:10, Cliff Woolley wrote:
> Taking a step back from gz for a moment, and speaking in general:
>
> On Sat, 1 Sep 2001, Ian Holsman wrote:
> > 3rd party modules are invisible to most people,
>
> I'll agree with that statement... we can tell ourselves that it's okay
> to push off modules onto third-party distribution, but the fact is
> that if it doesn't come as a standard module, people are much less
> likely to go get it unless they have absolutely no other choice
> because they either are too lazy, don't know it exists, or fear its
> stability/security because it's third-party.
>
> Perhaps modules distributed through official httpd subprojects are
> more visible/more trusted, but we don't really know one way or the
> other on that front yet.
I can agree with this, but this is something we need to fix. There are
many ways to fix it. Fixing modules.apache.org would be a very good
first step.
Putting every module into the core is NOT the answer to this problem.
IMNSHO, Apache should be a minamilistic web server. If we don't need it
in the core, it shouldn't be there. Personally, I would remove mod_dav
from the server too, because it doesn't implement part of RFC2616.
Ryan ______________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
Covalent Technologies [EMAIL PROTECTED]
--------------------------------------------------------------
