I've got a number of reports that are all nearly identical, except for the SQL they run, how they inflate the results, and which template basename they use. Right now, it's running under CGI, but I need to port it to mod_perl handlers.

The question I have is this how do I set up my stuff?

In my httpd.conf, I have the following:

PerlOptions -SetupEnv PerlWarn On PerlTaintCheck On PerlRequire /path/to/startup.pl <Location /reports> SetEnv ORACLE_HOME /where/oracle/lives SetEnv ORA_NLS33 /where/oracle/lives/ocommon/nls/admin/data SetHandler perl-script PerlResponseHandler My::Report::Handler </Location>

Do I have one handler that dispatches the report based on some HTTP param? Or, should I have an entry in httpd.conf for each report, along the lines of:

PerlOptions -SetupEnv PerlWarn On PerlTaintCheck On PerlRequire /path/to/startup.pl <Location /reports/report1> SetEnv ORACLE_HOME /where/oracle/lives SetEnv ORA_NLS33 /where/oracle/lives/ocommon/nls/admin/data SetHandler perl-script PerlResponseHandler My::Report::Handler1 </Location> <Location /reports/report2> SetEnv ORACLE_HOME /where/oracle/lives SetEnv ORA_NLS33 /where/oracle/lives/ocommon/nls/admin/data SetHandler perl-script PerlResponseHandler My::Report::Handler2 </Location>

What are peoples' experiences with this?

------
We are the carpenters and bricklayers of the Information Age.

The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

... strings and arrays will suffice. As they are easily available as native data types in any sane language, ... - blokhead, speaking on evolutionary algorithms

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.


In reply to Setting up mod_perl handlers by dragonchild

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.