Assuming the config and storage info is global (at least as seen from any particular call in the system), you can stuff them anywhere you like, but "logically" it would go either somewhere in the top model package or in a separate configuration package.

As for access, I'd recommend you use methods or regular subroutines that return the right data/object for the current context, since that way you can change the implementation without having to change all the code relying on the information.

update: as a variant of this, if the relevant info is all provided by the top-level model object, you can also make the model object globally available from a class method/subroutine and then get the data from there.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: Sharing data between children modules by Joost
in thread Sharing data between children modules by moltar

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.