You might want to use Apache::PerlRun instead of Apache::Registry unless you are
happy that your cgi scripts are "mod_perl safe".

      PerlRun is much better at handling non-compliant scripts. Although there's
      a performance hit against Registry, you'll still see a big increase over
      cgi.

      See the Guide for more....  http://take23.org/docs/guide/porting.xml

      HTH,

      Simon.






               From           "Slash" <[EMAIL PROTECTED]>        Date   15
January 2001
                                                                            
                                                                            
        To                                                                  
                "Tom Kralidis" <[EMAIL PROTECTED]>,   Time  17:31     
                [EMAIL PROTECTED]                                          
                                                                            


      Copy to         (bcc: Simon Wilcox/BASE/WilliamsLea)



      Bcc     Simon Wilcox/BASE/WilliamsLea



      Fax to



      Subject       Re: Mod Perl & Vhost





hmm.. I can't seem to figure this out.. cgi's are not working at all now..
hmmm
We have like 20+ vhost and I was thinking mod_perl would help us out alot..
We get around 200k+ hits a day and server load is unreal..   well thanks for
your help anyway..

[snip]

>
> <Location /cgi-perl/>
>   SetHandler perl-script
>   PerlHandler Apache::Registry
>   PerlSendHeader On
>   Options +ExecCGI
> </Location>
>
> ...










______________________________________________________________________


   This document should only be read by those persons to whom it is addressed
   and is not intended to be relied upon by any person without subsequent
   written confirmation of its contents. Accordingly, our company disclaim all
   responsibility and accept no liability (including in negligence) for the
   consequences for any person acting, or refraining from acting, on such
   information prior to the receipt by those persons of subsequent written
   confirmation.

   If you have received this E-mail message in error, please notify us
   immediately by telephone. Please also destroy and delete the message from
   your computer.

   Any form of reproduction, dissemination, copying, disclosure, modification,
   distribution and/or publication of this E-mail message is strictly
   prohibited.


Reply via email to