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 14:23:37 GMT

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


> William A. Rowe, Jr. wrote:
> > At 11:38 PM 8/24/2002, Joe Schaefer wrote:
>
> >> I'd rather the apreq filter behaved like a block-buffered filter would.
> >> AFAICT mod_deflate doesn't consume the whole body before passing it
> >> along,  so why do you think we need to?
> >
> >
> > No, we don't need the whole body.  The idea of pre-fetching 8kb, 16kb or
> > even 64kb is so that the variables are know up-front.  If someone needs
> > more, they simply need to call ap_get_brigade again until they have the
> > content they need.  And then it's their job to set aside the content for
> > the
> > next upstream filter or the final handler destination.
>
> What happens if you have a form with big input values, so that (e.g.)
> the last key/value won't feet into 8/16/64k. So when you call
> $r->params() (which is supposed to return all keys) you won't be able to
> get them all, meaning that you really have to suck the whole data in,
> before you know whether you have all the keys or not.

This is true, but it's a limitation of the content-type of the POSTed data,
not of HTTP or apreq.

  Issac



Mime
View raw message