> -----Original Message----- > From: Etienne Marcotte [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 24, 2001 12:13 PM > To: [EMAIL PROTECTED] > Subject: mod_perl > > > I read often about that mod_perl that makes perl run a lot faster and > etc.
mod_perl is an Apache module that integrates a full Perl interpreter into the Apache server. By using mod_perl, your server can execute perl code much more quickly, since it doesn't have to fork and load a full Perl binary and compile the script for each request. > I tought until now that it was "by default" mod_perl when > it's with the > apache distribution, but Brett stated: "and CGI::Carp has > some problems > when run under mod_perl" > > Does that mean a script has to be build for mod_perl and/or mod_perl > needs to be "called" in each script? Or mod_perl is not something I > should worry about and if it's with my Apache it means it's using > it...:-) When mod_perl is installed, you have the capability to define various perl handlers for Apache requests. This is *not* enabled by default; you must specifically configure Apache to send appropriate requests to a perl handler of your choice. There are two handlers available for use under mod_perl that emulate a CGI-type environment: Apache::PerlRun and Apache::Registry. With Apache::PerlRun, you can run regular CGI scripts unchanged and get many of the benefits of mod_perl. To use Apache::Registry, you need to possibly make some minor script changes, but you get even more speed benefits. You can also use other kinds of handlers that deal with requests in a variety of ways. If you want to understand mod_perl, get the "Eagle" book, Writing Apache Modules with Perl and C, by Lincoln Stein. Also, visit the mod_perl homepage at http:://perl.apache.org. There is also *tons* of documentation in the mod_perl guide at http://perl.apache.org/guide/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
