cbrandtbuffalo has asked for the wisdom of the Perl Monks concerning the following question:
This all works quite well for us for most config info. However, we've run into a strange situation with mod_perl. If you load config data just once per process, it works fine for pseudo-static information like machine environment and path info. But information that changes per-hit such as the current user (REMOTE_USER) needs to be loaded each time.
From a design perspective, where should that information live and how should it be loaded? Should we 'new' our config module on each hit and include per-hit data there (and re-run all the code), or should a config module contain only data that doesn't change once the process if fired up? Or should we have two modules?
Thanks for any insight.
Update: Did some research based on badaiaqrandista's response and found some information on scope in web apps that gives more detail.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: What config info belongs where for web apps?
by badaiaqrandista (Pilgrim) on Dec 14, 2005 at 00:50 UTC | |
by cbrandtbuffalo (Deacon) on Dec 14, 2005 at 13:43 UTC | |
by badaiaqrandista (Pilgrim) on Dec 14, 2005 at 22:59 UTC | |
Re: What config info belongs where for web apps?
by duckyd (Hermit) on Dec 13, 2005 at 23:12 UTC | |
Re: What config info belongs where for web apps?
by jhourcle (Prior) on Dec 14, 2005 at 00:31 UTC | |
Re: What config info belongs where for web apps?
by Mandrake (Chaplain) on Dec 14, 2005 at 03:19 UTC | |
Re: What config info belongs where for web apps?
by kulls (Hermit) on Dec 14, 2005 at 03:28 UTC |