Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 57926 invoked by uid 500); 25 Aug 2002 06:03:58 -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 57893 invoked from network); 25 Aug 2002 06:03:58 -0000 Errors-To: Message-Id: <5.1.0.14.2.20020825010241.031ecde0@pop3.rowe-clan.net> X-Sender: wrowe%rowe-clan.net@pop3.rowe-clan.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 25 Aug 2002 01:03:52 -0500 To: dev@httpd.apache.org From: "William A. Rowe, Jr." Subject: Re: dev question: apreq 2 as a filter? Cc: Stas Bekman , Joe Schaefer , Issac Goldstand , apreq list In-Reply-To: <3D6858D4.3090606@stason.org> 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> <036301c24bbb$59f45eb0$1a0aa8c0@deepthought> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Just a quick observation. The fact that the input filtering schema is a bit clumsy for apreq is a perfect example of WHY we should incorporate apreq into the Apache core. Without a good use case, input filters will never become as polished as they aught to be. Bill