Return-Path: Delivered-To: apmail-httpd-apreq-dev-archive@httpd.apache.org Received: (qmail 83620 invoked by uid 500); 26 Aug 2002 17:42:17 -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 83604 invoked from network); 26 Aug 2002 17:42:16 -0000 To: "William A. Rowe, Jr." Cc: Stas Bekman , Issac Goldstand , apreq list Subject: Re: dev question: apreq 2 as a filter? References: <"William A. Rowe, Jr."'s message of "Mon, 26 Aug 2002 09:08:47 -0500"> <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> <5.1.0.14.2.20020826090113.02da9e60@pop3.rowe-clan.net> <5.1.0.14.2.20020826122329.07398420@pop3.rowe-clan.net> From: Joe Schaefer Date: 26 Aug 2002 13:43:11 -0400 In-Reply-To: "William A. Rowe, Jr."'s message of "Mon, 26 Aug 2002 12:25:21 -0500" Message-ID: Lines: 29 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 "William A. Rowe, Jr." writes: > At 11:18 AM 8/26/2002, Joe Schaefer wrote: [...] > >For instance, it would be a bad thing if the content-handler injects > >apreq at the end of the filter chain, then "does something" to cause > >apreq to prefetch some post DATA, and *then* wants to inject utf-8 > >somewhere upstream from the apreq filter. > > That's easy... when you insert a filter, you can choose to insert it before > or after another filter. Any filter that wants apreq results before processing > it's own input filtering MUST insert itself behind the apreq filter, after > calling > the fn to inject and initialize the apreq filter. That's not the case I'm worried about. I'm worried about the case where the to-be-inserted filter wants to modify the input stream *before* apreq starts parsing it. The to-be-inserted filter isn't interested in the apreq data whatsoever. For example, someone may write a filter whose job is to run a SAX-ish XSL transform on the incoming "text/xml" data. (Perhaps even as a fixup for apreq's xml parser). We had better not have prefetched any of the POST before that filter is injected upstream. -- Joe Schaefer