> redundancy. However, it seems your philosophy would say that if there is > an admin interface to the data and a user interface, there should be two > separate CGI::App modules to implement these separate interfaces. That > seems like redundancy. There is some redundancy, but the recommended (Well, by me, but I know i've seen Jesse et al say similar things) way of doing the "work" of the script is to have a separate module: Admin.pm is a CGI::App subclass calls Do::Stuff->various_functions() to do stuff. User.pm is a CGI::App Subclass calls Do::Stuff->various_functions() to do stuff. Thus, only the differences in the interfaces are in the app modules, the "work" parts are in a separate module that those scripts call. And future modules can also call these modules. Non-cgi scripts can call these functions to do maintenance, or whatnot. While it appears to increase redundancy, in practice it reduces it. -- SwiftOne suppressed --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ To unsubscribe, e-mail: suppressed For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.