Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 69486 invoked by uid 500); 31 Mar 2003 22:18:39 -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 69471 invoked from network); 31 Mar 2003 22:18:38 -0000 From: TOKILEY@aol.com Message-ID: <10.2e9d912b.2bba18c2@aol.com> Date: Mon, 31 Mar 2003 17:18:42 EST Subject: Re: mod_deflate -- File size lower bound needed? To: dev@httpd.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: 7.0 for Windows sub 10637 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N FYI: There was a serious brain fart (mine) in the previous message... I said... >> 2. If there's no EOS in the brigade yet you have to assume >> more is coming so now it's nut-crackin' time. If the 'minimum >> file size' is less than the amount of data already in the first >> brigade showing up then it's also a no brainer... just pass >> it on without compressing. If the minimum file size is >> larger than what's in the first brigade... then it's time to >> start buffering ( if the code allows it ). What I meant was that if the 'minimum_file_size' is less than the amount of data already in the first brigade that shows up then you already know that this puppy is NOT 'below the minimum' and ( based on other criteria ) is eligible for compression. At this point it's is a sure-fire 'MAY' be compressed depending on other eligibilty checks.