Posted by AviCoh on 12/19/06 02:10

Janwillem Borleffs wrote:
> AviCoh@gmail.com wrote:
> > Also, I use the nice stream wrapper 'php://input' in order to read the
> > posted binary contents, and again here I notice that the control is
> > passed to PHP only after the entire request had reached the server.
> >
>
> A possibility would be to set up a PHP-based (telnet) server, which listens
> to a port ignored by Apache.
>
> http://www.devshed.com/c/a/PHP/Socket-Programming-With-PHP/
>
>
> JW

Thanks, JW.
However, I'm afraid it's not a viable (yet original :-D ) option for me
due to three reasons:
1. my hosting provider does not allow any incoming socket operations
(outgoing using curl via proxy only)
2. I wouldn't wanna go with any other port rather than 80 in order not
to have to deal with FW issues on the client side
3. I like what I get from Apache+PHP and wouldn't want to implement a
mini web server inside my app.

It just seems logical to me that PHP would support such a flow (like
perl or java for instance).

I have tried playing with some php.ini parameters :
changed the post_max_size to 0, and was able to receive the entire file
contents without having to wait for the request to finish.
The downside was that PHP kept screaming on that it had received a
request with a body bigger than the post_max_size....

Best,
Avi

[Back to original message]