> On Sun, Mar 03, 2002 at 10:34:55PM -0000, [EMAIL PROTECTED] wrote: > > rbb 02/03/03 14:34:55 > > > > Modified: modules/http http_core.c > > server core.c > > Log: > > Classify some of the input filters as the correct types. Previous to > > this patch, the type wasn't too important, because all filters were > > put on the same list. After this patch, the filter type is very > important, > > because there are three different types of filters, and they are all > treated > > differently, namely: > > > > CONNECTION: Filters of this type are valid for the lifetime of this > > connection. > > PROTOCOL: Filters of this type are valid for the lifetime of this > > request from the point of view of the client, this means > > that the request is valid from the time that the request > > is sent until the time that the response is received. > > 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"
YES, resource is markedly better than CONTENT. I have been using resource all day when explaining this to people at work. Always scary when Greg and I agree. :-) Ryan
