Anyway, I'm working in a system that has a number of CGI::Application classes, and I'm looking at converting some older non-CGI::App code into additional ones. Some of the new run modes will require a particular kind of authentication/login and should use an interstitial login phase before proceeding to the desired content. I don't want to bundle all those run modes into one monolithic class - I'd like them divided up by what part of the system they deal with. But I don't see a good way to provide the login phase to each class. At the moment, I'm planning a mixin class to provide the login-related run_modes, but something about that feels dirty.
Any suggestions?
In reply to juggling multiple CGI::Application subclasses by ysth
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |