Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 78934 invoked by uid 500); 22 Nov 2002 11:03:44 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 78921 invoked from network); 22 Nov 2002 11:03:44 -0000 Message-ID: <3DDE0F1C.7050807@apache.org> Date: Fri, 22 Nov 2002 12:03:56 +0100 From: Henri Gomez User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en, fr MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: [PATCH] mod_deflate extensions References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > I also refer you to the discussion thread regarding the > original inclusion of mod_deflate which contains some > 'advice' posted to the Apache forum from Dr. Mark Adler > ( one of the original authors of all this GZIP/ZLIB LZ77 > code ). > > He suggested that compiling your OWN version of GZIP/ZLIB > was pretty much the only 'sane' thing to do and I agree > 100%. There are actually a number of 'flaky' distributions > of GZIP/ZLIB 'out there'. > > He ( Mark Adler ) himself pointed out that there are > some 'patches' floating around for GZIP/ZLIB that never > made it into ANY standard distribution and only by applying > them yourself to your own compiled OBJ/LIB could you be > sure what you are actually using and what shape it is in. So we should use a copy of mod_gzip compression code in Apache 2.0. Also as someone involved in mod_jk/jk2, I'll need gzip compress/uncompress support in Apache 2.0 for a new ajp protocol I'm working on, so having compression/uncompression in Apache 2.0 will be mandatory for me. > If they REALLY WANT some 'feature' in their Server... they > will tough it out and get it done. That's the way it's > always been with Apache so no one would be shocked if some LIB > wasn't in the right place or a makefile needed tweaking. Ok, let be pragmatic. Did Apache HTTP developpers agree that compression should be added in Apache 2.0 by incorporating mod_gzip comp code in Apache 2.0 ?