Dmitry Beransky <[EMAIL PROTECTED]> wrote:
>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. It should also be possible to
>have $r->read return the cached data even when called from an internal
>redirect (by delegating calls to $r->prev->read, etc). As the size of a
>request body can be arbitrarily large (e.g. file uploads), perhaps it would
>be better not to have the caching behavior turned on by default, but rather
>enable it on a per-request basis.
>
>Again, this is all hypothetical. Can anyone comment on feasibility (and
>usefulness) of such a feature?
This would be very nice, but looking through the source code for Apache last
week, the socket connection is closely tied to it's idea of stdin for POST
operations. I could not find a way to present the body of the request to
arbitrary handlers. Hopefully Apache 2.0 can eliminate this problem with the
layered I/O that I've heard rumors about.
--
James Smith <[EMAIL PROTECTED]>, 409-862-3725
Texas A&M CIS Operating Systems Group, Unix
