Re: [cgiapp] CGI::Application::Displatch v2, and CGI uploadInfo wierdness

[Rhesa Rozendaal <suppressed>]

Dan Horne wrote:
> > From: David Steinbrunner
> >
> > I have a system running under lighttpd/CAD v2/FastCGI/OpenBSD 
> > and file uploads work for me.  My file uploads are small and 
> > hence have not run into any timeout issues so the upload 
> > processing runmode runs just like all my other runmodes.
>
> Unfortunately, the site admins are uploading hi-res photos, and can load as
> many as they like at once, so I need to keep the upload happening. There may
> be some kind of Ajax solution that provides a heartbeat of some kind, but
> CGI seems to work for me ok (plus I'm not hogging a whole persisent copy of
> a memory-hungry app for the length of the upload)

I wouldn't worry about it: we (at ExposureManager) also run image uploads 
through plain CGI. We can't afford to tie up expensive mod_perl instances for 
too long: a single image might take as much as 5 minutes to upload (or more, 
depending on the client's internet connection). A single mod_perl instance 
might serve more than 300 other requests in that time!

An additional advantage is that you can increase the web server's timeout for 
uploads independent from the rest of your app. And it's easier to farm out 
those requests to separate machines too.

IMHO, running file uploads through plain CGI is the most sensible approach.

Rhesa

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
             http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed