For the complex programs on the site I'm building I will be using
CGI.pm, but there are a few parts of the site where there is little
browser-server interaction other than to send a certain page based on the
query string and a cookie. Because these pages get refreshed a lot I'm
thinking that using a mod_perl based alternative to CGI.pm might be a good
way to coax a little extra out of the server.
It would only be used once per request from the browser. Would this
make a difference since it will be used multiple times on a process, but
only once per request?
Kevin
----- Original Message -----
From: "Paul" <[EMAIL PROTECTED]>
To: "Kevin Schroeder" <[EMAIL PROTECTED]>; "modperl"
<[EMAIL PROTECTED]>
Sent: Monday, July 09, 2001 3:09 PM
Subject: Re: CGI module or Apache
>
> --- Kevin Schroeder <[EMAIL PROTECTED]> wrote:
> > Hello,
> > I've been using the CGI PERL module for a while now and I like
> > using it a lot. But I was wondering if using that module with
> > mod_perl will slow things down because of the extra module being
> > used. If so, is there a way to use the Apache API and mod_perl to
> > deal with form submissions, cookies and the like? You'll have to
> > forgive me, I've been learning mod_perl off of the cheat sheet at
> > refcards.com.
>
> lol -- well, we don't *HAVE* to forgive you.... ;o]
>
> The CGI module is your best bet for most processing of those sorts, but
> you can still use mod_perl. Anything you add will swell the footprint
> of your server a bit, but if you have the resources, CGI.pm is worth a
> little bloat.
>
> Just use it in your handlers normally. It'll only be included once per
> process, . . . right?
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail
> http://personal.mail.yahoo.com/
>
