httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Issac Goldstand" <mar...@beamartyr.net>
Subject Re: dev question: apreq 2 as a filter?
Date Mon, 26 Aug 2002 08:09:11 GMT

----- Original Message -----
From: "Stas Bekman" <stas@stason.org>
To: "Joe Schaefer" <joe@sunstarsys.com>
Cc: "William A. Rowe, Jr." <wrowe@rowe-clan.net>; "Issac Goldstand"
<margol@beamartyr.net>; "apreq list" <apreq-dev@httpd.apache.org>
Sent: Monday, August 26, 2002 10:07 AM
Subject: Re: dev question: apreq 2 as a filter?


> Joe Schaefer wrote:
> > Joe Schaefer <joe@sunstarsys.com> 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 :-)
>
> The things that I see weird about this is that the normal filter is not
> supposed to call ap_get_brigade more than once. our apreq_ filter calls
> ap_get_brigade more than once, because if it doesn't, there is no way to
> consume the data (the response handler) will usually not ask for the raw
> body. So apreq_ is really a semi-filter, since it acts as a filter and
> consumer at the same time.

Not necessarily.  My example from yesterday proposed two distinct operating
"modes"; one which will do this, and the other default one, which will not.

  Issac



Mime
View raw message