On Sun, 19 May 2002, Stas Bekman wrote:
> I beg your pardon? I cannot find any reference of you saying anything
> regarding $r->content.
i'm certain i've at least stated several times that $r->content and
$r->args in-an-array-context were mistakes that never should have been
part of the api. and was pretty sure most the reasons why were well known
too. anyhow, here's a couple of reasons:
- does not handle multi-value keys
- does not handle multi-part content types
- does not handle chunked encoding
- slurps r->headers_in->{'content-length'} into a single buffer
(bad for performance, memory bloat, possible dos attack, etc.)
- in general duplicates functionality (and does so poorly) that is done
better in Apache::Request
- if one wishes to simply read POST data, there is the more modern
{setup,should,get}_client_block api, and even more modern filter
api. along with continued support for read(STDIN, ...) and
$r->read($buf, $r->headers_in->{'content-length'})
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
