Re: Advice on Apache

[John S. <js...@im...>]

>Thanks for all the replys. After doing further reading
>I came to the conculsion that I didn't need mod_perl.
>I have Apache now installed. now for DBI.
>Wayne
>
>"Roderick A. Anderson" wrote:
>
>>  On Thu, 12 Jul 2001, Jonas Smedegaard wrote:
>>
>>  > On Thu, 12 Jul 2001, Wayne wrote:
>>  >
>>  >  > Thanks for the input John. I download Apache 1.3.20 and after reading
>>  >  > the INSTALL instruction I'm not sure whether I should install mod_perl
>>  >  > first or if I can do it after installing Apache.
>>
>>  You might look for the apache-heavy package - statically linked in
>>  mod_perl (and other modules if you want). There are RPMs (which is what
>>  I use) but I'm not sure about a tarball or other package managers.
>>
>>  > Forget about mod_perl. For SQL-Ledger you need Apache and perl, not
>>  > apache+perl.
>>  >
>>  > mod_perl is for embedding perl commands in html - like server side
>>  > includes or php. SQL-Ledger is perl CGI-scripts, not embedded perl.
>>
>>  Actually I think you're thinking of embperl.  Mod_perl loads a perl
>>  interpreter into Apache.  The main benefit being quicker startup of perl
>>  scripts.  Instead of Apache making a system call to the script which
>>  starts perl which reads the rest of the script file to execute; mod_perl
>>  gets reads the script to execute (or it will already be there from a
>>  previous call).  Things happen faster.
>>
>>     For a lightly loaded server (hardware and software wise) it isn't
>>  really needed but on a system running multiple companies which may have
>>  multiple users connected at the same time the response times would be
>>  much better.
>>
>>  I'm not sure if the SQL-Ledger code supports Apache::DBI but it is my
>>  understanding that this in conjunction with mod_perl will make a
>>  significant response time difference.
>>
>  > The short of it is mod_perl isn't needed for light/normal usage.

This thread has raised an interesting point regarding Doug 
MacEachern's mod_perl, a truly powerful resource. Apparently, it's so 
popular that many CGI developers have switched to circumnavigate 
mod_cgi's shortcomings. Statistics at 
http://perl.apache.org/netcraft/ show it in use on over 2 million 
server installations.

Obviously there is an advantage to mod_perl's persistence, speeding 
up response processing significatively (I've seen claims of 
improvements in the order of 10 to 100 times!, depending on code) in 
exchange for a bit more RAM. This is clearly a usable benefit!

Where do you all think mod_perl can fit into sql-ledger's scheme of things?



John