in reply to your mod_perl configurations

Did you have a specific question or problem you are having? Or did you just want to see some examples?

Your example looks fine, as long as coders on the system know that if they put things in that directory they will be run under Registry. If you're concerned about limiting this, you can designate specific scripts, as suggested above.

If you are using a database, you should also look into Apache::DBI. This module manages persistent DB connections and this can give you a significant performance increase. Plus you aren't hitting your DB with constant connects and disconnects.

Replies are listed 'Best First'.
Re^2: your mod_perl configurations
by lima1 (Curate) on Feb 17, 2006 at 02:18 UTC
    my "question" was, are there some useful mod_perl features you can add just in your apache conf instead of changing too much sourcecode. or using other modules instead of this Registry, that protect you from simple DoS attacks, whatever, nice features you use and that i can use and understand without reading 300 pages of the modperl book. sorry if this was a stupid question, I'm a mod_perl newbie.
[reply]
      Not a stupid question at all; I just wasn't clear what it was. :)

      Registry pretty much does the trick. Some modules to check out are Apache::DBI and possibly Apache::Template.

      As far as getting into special settings in the server, that's where you get advanced. mod_perl gives you full access to Apache internals via perl code in handlers. Once you start writing handlers, you can respond to requests however you like, but you'll need to read a decent amount of documentation before you can really take advantage of these features. Note that this requires knowledge of Apache as much as mod_perl.

[reply]

In Section Seekers of Perl Wisdom