Yes, I agree. But as (I thought) I had mentioned in an early post, it
should be possible to turn on this caching behavior for each individual
request before a call to $r->content or $r->read.
Cheers
Dmitry
On 28 Oct 1999, Greg Stark wrote:
>
> That makes sense for small pieces of data such as might be posted by a browser
> from a typical form. But browsers doing a file upload could send huge amounts
> of data, possibly many megabytes. Trying to store all of it in memory would be
> a bad idea. Also, not every HTTP client is a web browser, some POST form
> submissions could be huge transactions even without a file upload.
>
> Dmitry Beransky <[EMAIL PROTECTED]> writes:
>
> > My apologies for continuing this topic, but I've been thinking some more
> > about this issue over the weekend. I'm still perplexed by this seemingly
> > arbitrary limitation on the number of times a request body can be read. It
> > seems that, at least theoretically, it should be possible to cache the
> > result of $r->content() or even $r->read() the first time it's called and
> > return the cached data on subsequent calls.
