Here's what our experienced peers have advised me earlier. Thanks
guys....it's been a great help!
Richard Dice says:
Your "regular old CGI Perl scripts" are going to be ported to mod_perl
most easily using one of 2 different Apache/mod_perl modules:
* Apache::Registry
* Apache::PerlRun
To be _really_ simplistic about it, Apache::Registry is faster, but it
is more picky about the quality of your Perl CGI programs, insofar as
quality is a measure of ability to hold up in a persistent environment.
Apache::PerlRun is slower, but your scripts are going to handle a better
chance of working without modification. (Another aspect of how it's
slower is that you won't be able to take advantage of Apache::DBI persistent
database connections with Apache::PerlRun.)
Here are some helpful links from Sta's mod_perl guide online:
CGI to mod_perl Porting. mod_perl Coding guidelines.
http://perl.apache.org/guide/porting.html
Apache::PerlRun
http://perl.apache.org/guide/porting.html#Apache_PerlRun_a_closer_look
****************************************************************************
************
Vivek Khera says:
The perl stuff will need to be "cleaned" if it is sloppy code. That
is, if it is clean running in Perl under "-w" and "use strict" you're
most likely going to have little difficulty with them.
But what you should do is use the two-server performance enhancement
(using mod_proxy and mod_rewrite) and have your legacy apps run on the
front-end server, and then migrate your perl to the mod_perl backend
one at a time.
****************************************************************************
************
Now, isn't that helpful? :)
-Pramod
At 05:29 PM 7/18/00 -0500, Glen Lee Edwards wrote:
>Is there any difference in the way I'd have to write my perl scripts if
>using mod_perl? I have a small commercial web server, run a perl web ring
>and talk list program on it as well as several other small perl
>applications. It sounds to me like installing mod-perl would decrease the
>overhead on my processor, but I simply don't have the time to go through
>and rewrite all those scripts.
>
>Glen
>
>
>
>On Tue, 18 Jul 2000 [EMAIL PROTECTED] wrote:
>
>>Sure. mod_perl makes it so your web server doesn't have to invoke the
>>Perl interpreter for every single hit. That alone makes mod_perl worth
>>it.
>>
>>There's a lot of other stuff it does, of course, but that's a huge win in
>>itself.
>>
>>Doug
>>
>>
>>On Wed, 19 Jul 2000, ozbcoz wrote:
>>
>>> or is that a "too big" question
>>>
>>> I am coding in Perl - not well but adequately (I use PHP for anything
>>> "hard"). Is there a compelling reason to switch to mod_perl ?
>>>
>>> Jim Carey
>>>
>>>
>>
>>
>
