Yes, right about the cleanup handler.

Your Apache::Reload idea sounds fine, but the code to stat a file and run your config parser again is awfully simple so don't be afraid to just write it.

I don't think there's much difference between the config modules in terms of reliability (it's a fairly simple task), but for determining memory footprint I think you will just have to load them into memory to see. Larger files usually lead to more memory, unless the file is mostly POD.

Don't worry about file locking. When you want to update your config file, just do it with a rename, i.e. mv myconfig.conf.new myconfig.conf. That should be an atomic update.

In reply to Re: Re: Config parsing module for mod_perl app? by perrin
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.