Andy has asked for the wisdom of the Perl Monks concerning the following question:

To increase my script(s) speed I am thinking about using Apache::Registry.

Here is the question: Because I do not own my own server (yet) I am hosted by someone with the CPanel control panel.

With adding: 

#in httpd.conf

 Alias /perl/ /perl/apache/scripts/ #optional
 PerlModule Apache::Registry

 <Location /perl>
   SetHandler perl-script
   PerlHandler Apache::Registry
   Options ExecCGI 
 </Location>

[download]
Does that affect all scripts?

Do 'I' or anyone need to put use Apache::Registry; ?

Thanks in advance,
Andy

Edit by tye

Replies are listed 'Best First'.
Re: Apache::Registry
by grantm (Parson) on Dec 18, 2002 at 07:30 UTC

    If I understand your question correctly, you want to know if you need to include ...

    use Apache::Registry;

    ... in your scripts. The answer is no.

    Apache::Registry is a special type of module known as a mod_perl handler. To oversimplify things a bit, it reverses the normal relationship and 'uses' your script :-)

    The configuration snippet you quoted is a way of telling Apache that any URL that starts /perl/ should be handled by Apache::Registry which in turn will look in /perl/apache/scripts/ for a specific script to handle each request. This is an alternative to using Apache's 'ScriptAlias' directive to have requests that start /cgi-bin/ handled by mod_cgi.

    Setting up a handler this way affects all scripts in the directory.

    Update: I forgot to mention that your coding needs to be a bit more careful under Apache::Registry than under CGI. Make certain your script runs with 'use strict;' and make sure that any global variables are declared with 'our' rather than 'my'. You'll also want to check the error log for warnings.

[reply]
[d/l]

      On a more general level, all your PERL-scripts which run under mod_perl must be coded carefully, as they probably get only compiled once for a multitude of requests and therefore the old contents of variables my linger on long after they should have died under a non mod_perl run script.

      The use of strict is not only recommended it is almost indispensable to guard against careless programming style.
      That and make sure that you initialize all your variables (either explicitly or trough the use of my) as you cannot count on them being 'virgin'.

      CountZero

      "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

[reply]
      I dont really want it to affect all scripts on the server. So if the first line of the httpconfig bit is only my directory it will be ok?
[reply]

        It won't affect all scripts on your server, but it will affect all scripts in /perl. The reason is that your <Location> directive associates Apache::Registry with /perl.

[reply]
        Yes.

        rdfield

[reply]
Re: Apache::Registry
by cLive ;-) (Prior) on Dec 18, 2002 at 09:09 UTC
    Every time you call a script beginning /perl/ after the domain, Apache treats it as mod perl. So say you had this mapping: 
    Alias /perl/ /home/public_html/mod_perl/
<Location /perl>
   SetHandler perl-script
   PerlHandler Apache::Registry
   Options ExecCGI 
 </Location>

    [download]
    And let's also say that your web root dir is /home/public_html and that your have enabled script execution throughout your site, then calling the script as: 
    /perl/script.cgi

    [download]
    would invoke it under mod_perl, whilst calling it under the more appropriately named :) mod_perl, following existing directory mapping, ie: 
    /mod_perl/script.cgi

    [download]
    would not.

    Bet you're totally confused now - sorry, it's very late...

    .02

    cLive ;-)

    ps - to answer your question, only those in the 'perl' directory.

[reply]
[d/l]
[select]

Back to Seekers of Perl Wisdom