On Sat, Mar 13, 2010 at 11:00 AM, Chris Travers <[email protected]> wrote:
> I am thinking of suggesting two global namespaces
>
> In package LedgerSMB
>
> use Class::Struct LedgerSMB::Globals => {
> user => 'LedgerSMB::User',
> session => 'LedgerSMB::Session',
> config => 'LedgerSMB::ConfigFile',
> # Config settings, similar to Sysconfig today
> };
>
> our Globals = LedgerSMB::Globals->new();
Just to note, this would mean calls would look like:
LedgerSMB::Globals->user->username
and
LedgerSMB::Globals->config->globals->{auth_method};
>
> in pacakge LedgerSMB::Web:
> use Class::Struct LedgerSMB::Web::Globals => {
> session => 'LedgerSMB::Session::Web',
> request => 'LedgerSMB::Web::Request',
> };
>
> our Globals = LedgerSMB::Web::Globals->new();
>
> Any other globally accessible information that needs to be available
> globally through apps/scripts?
Follow-up question: Should we have a separate .ini file for web
application configuration?
Best Wishes,
Chris Travers
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ledger-smb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
