Meanwhile, back at the ranch...
> My questions is how slow in seconds can a CGI be, before it is too
> slow for Mod_Perl to help?
This depends on how frequently it's requested. If it's rarely requested
than keep it as a CGI. The fewer applications you can keep out of the Web
server process,
> If each transaction lasts a
> couple of seconds, it this a Bad Thing?
>
I have always wondered about the point of using Mod_Perl vs Mod_CGI
where the program takes a couple of seconds to run completely.
To put it another way. Mod_Perl saves you some valuable time
which can make a difference
On Mon, 15 Nov 1999, Todd Finney wrote:
> process for the duration of the transaction? If each transaction lasts a
> couple of seconds, it this a Bad Thing? Is there a more efficient way to
> handle this?
Unless you truly need to resize the image on the fly as part of the
transaction with the
One solution is to use the 2 server setup described at
http://perl.apache.org/guide/scenario.html#One_Plain_and_One_mod_perl_enabl
and have the lightweight proxy server handle the upload as a regular
CGI process, after the file has uploaded redirect to a mod_perl
process for further processing. Yo
On Mon, Nov 15, 1999 at 01:14:43PM -0500, Todd Finney wrote:
> We're putting together a site that involves processing images uploaded by
> our users. I'm using Image::Magick to resize the images to a standard
> size, and to create thumbnails.We will have an upload page, which hits
> a CGI u
We're putting together a site that involves processing images uploaded by
our users. I'm using Image::Magick to resize the images to a standard
size, and to create thumbnails.We will have an upload page, which hits
a CGI under mod_perl that handles the form data and processes the image.
I a
