Re: cgi stdin buffer

--- bill lam <bbill.lam-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:

> Oleg Kobchenko wrote:
> > Shouldn't uploading be just a matter of parsing
> > stdin with mime sections?
> 
> I meant uploading 1MB is simple but not so trivial for uploading 100MB. I 
> think 
> that http server is smart enough to handle it but may be tricky for cgi. perl 
> cgi.pm seems automatically save data to a temp file, and then cgi program 
> then 
> open this temp file for reading.

Saving to temp files is a typical way of handling
uploaded files, but not the only one. It is the
responsibility of the CGI program (with help of
a library), but web server just streams it via stdin.
Technically the stdin mimes can be consumed on the fly
if, for example, they are meant to be stored in a database
instead of files.

That's the reason I was proposing buffered (streamed) 
stdin reader. With a streaming mechanism, large quantities
of data can be handled with very low memory footprint.



 
____________________________________________________________________________________
Looking for earth-friendly autos? 
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/