I'm not sure I completely understand how your solution differs from that suggested by tobyink (but then, I'm not sure I completely understand his solution... sorry, I don't have much experience with all this!)
How are the global variables in the AppGlobals module assigned their values? Does the dbh, cgi, session, etc, have to be passed into AppGlobals first? In that case, don't I just simply end up having to pass the AppGlobals object to every one of my subroutines? I suppose this does reduce the argument list from 3 items to just 1 item.
Or are you suggesting that the CGI object, session and DB handler are actually created inside the AppGlobals package, and then I access them using AppGlobals::get_dbh, AppGlobals::get_cgi, etc? So really it would be like the solution proposed by Anonymous Monk, except moved into a separate package?
I'm sorry if I'm missing something that should be obvious...
In reply to Re^2: Best practices passing database handles, cgi objects, etc.
by xtpu2
in thread Best practices passing database handles, cgi objects, etc.
by xtpu2
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |