Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 80232 invoked by uid 500); 5 Mar 2002 18:10:59 -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 80212 invoked from network); 5 Mar 2002 18:10:59 -0000 Mime-Version: 1.0 X-Sender: jimpop@devsys.jagunet.com Message-Id: In-Reply-To: <20020304175344.C13476@lyra.org> References: <20020303223455.12623.qmail@icarus.apache.org> <20020304175344.C13476@lyra.org> Date: Tue, 5 Mar 2002 13:11:00 -0500 To: dev@httpd.apache.org From: Jim Jagielski Subject: Re: the three filter types (was: cvs commit: httpd-2.0/server core.c) Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N At 5:53 PM -0800 3/4/02, Greg Stein wrote: > > CONTENT: Filters of this type are valid for the time that this >> content is used to satisfy a request. For simple requests, >> this is identical to PROTOCOL, but internal redirects >> and sub-requests can change the content without ending >> the request. > >Just wanted to state that I believe Ryan has the correct distinction here -- >that we have three types of filters. However, the third type is a misnomer, >and we can derive the proper name from the HTTP model: "resource" > Cool (on the above as well as the ideas for 2.1). I agree that RESOURCE is more clear. -- =========================================================================== Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson