I assume that you suggest a cleanup handler since it runs after a request, so the user sees no performance hit, but correct me if I'm wrong, please. And the reason that I'm in favor of moving to a CPAN module was an attempt to make the code more modular and maintainable. (And, yes, my use of a tied hash is probably unnecessary. :-)

(While mulling this over, I thought of the following idea, but maybe it's overkill. Use Apache::Reload with PerlSetVar ReloadAll Off. Then, use PerlSetVar ReloadModules to explicitly register my config-reading module. However, then I PerlSetVar ReloadTouchFile to the name of the config file. That should have the effect of only reloading my config-reading module whenever the touch file changes, and since the touch file will be the config file itself, that should have the desired effect.)

So, anyway, I've got some good ideas to work with. Thanks to those who replied. I'm still left with one question, though: what's the lightest weight yet reliable config-parsing module out there? And one that properly handles file locking in case of multiple concurrent requests, as well?

-jehuni

In reply to Re: Config parsing module for mod_perl app? by jehuni
in thread Config parsing module for mod_perl app? by jehuni

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.