in reply to Breaking up Large Modules.
Personally, I think you went about things the wrong way. Normally, one doesn't specialize, then shoehorn them back into the general case. Remember - you can use more than one .cgi in your "application". CGI::Application is really misnamed. It should be called CGI::ApplicationComponent. My current CGI app is actually made up of
That's all in one web application. Each of them has their own class that inherits (indirectly) from CGI::Application. One C::A developer told me that if any of his C::A classes has more than 8-12 runmodes, he has to find a reason not to refactor it into more than one C::A class, with its own .cgi wrapper.
------
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
|
|---|