in reply to Getting started with mod_perl

On the official site they only have a Apache2::Registry and a "module", not a regular mod_perl page! I'm working fine with Registry.
What do you mean by regular mod_perl page?

http://perl.apache.org/docs/2.0/user/index.html
here you can get randy kobes discontinued apache2/perl distribution (has sample config with mason/tt2 ... )

Replies are listed 'Best First'.
Re^2: Getting started with mod_perl
by John M. Dlugosz (Monsignor) on Jul 14, 2008 at 06:31 UTC
    Using "Registry" goes to some effort to run CGI scripts unchanged. I don't need that, as I'll write to the API. The "module" or "handler" is set up differently, with the Apache config file mapping a URL to the file to run, instead of the file just being there at that location. So you have to put every single such file into the configuration.

[reply]

      So you have to put every single such file into the configuration.

      This is not necessarily the case. I tend to have a single entry point to my mod_perl application (a dispatcher), which handles everything below / except for (eg) paths to static content: 

      
        <Location ~ "^/(?!img|stylesheets|scripts|robots.txt|favicon.i
+co|error).*" >
            SetHandler          perl-script
            PerlResponseHandler My::Dispatcher
        </Location>

      [download]

      and that single handler parses the request, then hands it off to the relevant handler in my code. Once that handler has processed the request, it passes back the relevant data, template name etc, and my dispatcher handles the template processing and returns the correct response.

      This allows you to do pretty much everything in Perl, without having to worry too much about apache.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom