Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 52367 invoked by uid 500); 2 Oct 2000 23:35:27 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 52356 invoked from network); 2 Oct 2000 23:35:27 -0000 Errors-To: From: "William A. Rowe, Jr." To: Subject: RE: cvs commit: apache-2.0/src/main http_core.c http_protocol.c Date: Mon, 2 Oct 2000 18:35:26 -0500 Message-ID: <000601c02cc9$720bd2c0$92c0b0d0@roweclan.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 In-Reply-To: Importance: Normal X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > From: rbb@covalent.net [mailto:rbb@covalent.net] > Sent: Monday, October 02, 2000 6:13 PM > > Being a static function doesn't mean it must be placed by the core > filter. As long as the function can be named at some point, it can be > added by anybody. This is why I want this as a part of the core > filter. Doing the buffering in multiple places, or anyplace > other than > the core filter is a bit bogus. Anything but... silly example, mod_random. Ok, you want to maximize the random results ... you need to place the buffer filter before mod_random, after mod_autoindex. Otherwise we end up with single lines in sequence, not randomized, since the mod_random fitler is only given one line each iteration. I entirely agree with Greg that we do -not- want every author to reinvent filtering. Bill