Hi all,
I did a brief search of the archives, and the web, but found few ideas that address this issue... which seems odd, because this is a very common problem with typical mod_perl applications. What I have is a large distributed mod_perl application, with many packages strewn throughout a hierarchy of classes on the filesystem of a server. This application code is either replicated to different servers, or shared over a read-only NFS partition. Each server needs to be able to set a small number of constant global options at compile time, which should be stored in a configuration file on the local filesystem. So, is there an accepted, right way to suck in a local configuration file at compile time? And, what's the best way to scope these "globals" so that they are visible to the classes and subclasses in the system that need to read them? I want to keep coupling to a minimum, as there is a lot of reused and reusable code. Again, these values can and should be considered immutable during execution. RTFM answers gratefully accepted :-) Thanks! - Ryan -- Ryan Thompson <[EMAIL PROTECTED]> Network Administrator, Accounts SaskNow Technologies - http://www.sasknow.com #106-380 3120 8th St E - Saskatoon, SK - S7H 0W2 Tel: 306-664-3600 Fax: 306-664-1161 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America
