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

["Dan Horne" <suppressed>]

-----Original Message-----
> From: John Saylor 
> 
> hi
> 
> > From: Rhesa Rozendaal
> > 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:
> 
> ?
> 
> how is mod_perl more expensive than CGI- by what measurement?
> performance speed?
> memory usage?
> development/maintenance cost?
> 
> you also talk about dedicating a server to this task, or farming it out
> to several servers. but that's hardware and you could do that with
> either mod_perl or CGI.
> 
> my own experience has been that the mod_perl libraries are better in
> just about every measurement than CGI.
> 
Well, if you're uploading 20GB of photos then don't you think mod_perl is a
bit of overkill? From my perspective, you use mod_perl for 2 reasons: One is
to get access to Apache's internals, which I don't need in this case. The
other is for performance, but for uploading large amounts of data, the speed
benefits are negligible in the context of the time to process the whole
request - and mod_perl is a lot more resource intensive than CGI, and I'd be
wasting a lot of memory. As I pointed out I use a persistent environment for
everything apart from file uploads (although I'm using FastCGI. If it was
still supported, my preferred environment would PersistentPerl/SpeedyCGI)

Dan


---------------------------------------------------------------------
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