httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: [rfc] [apreq-2] filter prefetch
Date Fri, 18 Jul 2003 07:36:11 GMT
Joe Schaefer wrote:
> Assuming the POST data hasn't been read by the 
> content handler,
> 
>   my $foo = $req->param("foo");
> 
> causes mod_apreq to prefetch 64KB of POST data
> in order to find the "foo" param.  But what about
> list context?
> 
>   my @foo = $req->param("foo");
> 
> Here the caller is expecting the full set of "foo"
> params, so it seems natural to me that we should have
> mod_apreq (i.e. the filter) parse the full POST body 
> for this case.  However, since mod_apreq is a filter,
> we have to be careful not to let the spooled POST data 
> consume lots of RAM.  
> 
> Earlier today I committed a patch that allows mod_apreq 
> to spool a large (>250KB) POST into a tempfile bucket,
> similar to the manner in which the mfd parser spools
> a large file upload.  If folks are ok with this approach,
> I'll make the necessary changes to the perl glue and
> endow $req->parse with these semantics as well.

Are you talking about having a copy of the POSTed data and another copy of the 
parsed data, when you are saying:

    we have to be careful not to let the spooled POST data
    consume lots of RAM.

Otherwise what's wrong with using all the needed RAM for the POSTed data? 
There is a limit argument which tells how big POSTed data can be, no?

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


Mime
View raw message