In any web application bigger than a toy, the C::A classes are going to be less than 20% of the actual code. The rest of the work should be done in business-layer classes. For example, I have a C::A reporting application. The reports are defined in their own classes. The C::A stuff has 2-3 runmodes that dispatch to the appropriate report class. C::A - maybe 200 lines. The reports, parameters, and templates - 2000++ lines.
If you decompose correctly, you shouldn't be working in the C::A hierarchy unless you're changing user interactions.
- In general, if you think something isn't in Perl, try it out, because it usually is. :-)
- "What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?"