Return-Path: Delivered-To: apmail-httpd-apreq-dev-archive@httpd.apache.org Received: (qmail 71171 invoked by uid 500); 25 Aug 2002 15:04:16 -0000 Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list apreq-dev@httpd.apache.org Received: (qmail 71158 invoked from network); 25 Aug 2002 15:04:15 -0000 To: "William A. Rowe, Jr." Cc: "Issac Goldstand" , "apreq list" Subject: Re: dev question: apreq 2 as a filter? References: <200208212349.40583.chatgris@mediapow.com> <3D647453.7030704@stason.org> <3D651310.3050008@stason.org> <5.1.0.14.2.20020822123542.02919dc8@pop3.rowe-clan.net> <3D65AF9D.7060908@stason.org> <3D65CA9A.4050706@stason.org> <5.1.0.14.2.20020823035453.02bf93b8@pop3.rowe-clan.net> <3D6602E1.9070600@stason.org> <5.1.0.14.2.20020825004851.02a71ea0@pop3.rowe-clan.net> From: Joe Schaefer Date: 25 Aug 2002 11:05:06 -0400 In-Reply-To: Joe Schaefer's message of "25 Aug 2002 10:12:31 -0400" Message-ID: Lines: 18 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Joe Schaefer writes: [...] > I think the apreq filter can/should operate in a completely > transparent way, since all it has to do is read a copy of the buckets > into the apreq_list _as the upstream_ _filters dictate_. Every time > our filter is invoked, it can make a stab at parsing the apreq_list > data, so the list should never get very big. Um, you may need to s/upstream/downstream/g in everything I wrote in the aforementioned post. It'd be nice if what I write actually matched the picture in my head :-) ENOCAFFEINE, sorry about that. -- Joe Schaefer