Thanks, Rob.

If the the raw upload file is to be saved in the local server, Nginx
has good performance.
But I want to compress the upload file and split it and then transfer
to another central storage system,
the file is not to be stored locally.

In fact, the problem is that, if there's 1000 concurrent requests,
each request has 500MB post body,
It's to comsume 500G temporary disk space, and it will take a lot of
time to process these data too.

So, I think that if there's stream processing support, It will be
better under this application.

On Fri, Mar 19, 2010 at 10:56 PM, Rob Schultz <rschultz7@gmail.com> wrote:
>
> On Mar 19, 2010, at 2:25 AM, li zJay <zjay1987@gmail.com> wrote:
>
>> This is really a problem for those who want to use Nginx as a
>> file-upload server.
>
> Why do you suggest that? This prevents your application worker processes
> from being tied up waiting for uploads. If you need something like upload
> progress there is a module for that
> http://wiki.nginx.org/Nginx3rdPartyModules#Upload_Progress_Module
>
> v/r,
> Rob
>


--
zJay

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx