It depends, controllers are part of the presentation layer, if there is business logic it could be factored onto objects ( models ) it belongs to. If it is repetitive presentation logic you could sub-class the Zend_Controller_Action or create action helpers if the repeating logic are "cross cutting concerns". Keep in mind the saying is "fat model thin controller" not just "thin controller"
Recommended reading - http://blog.astrumfutura.com/archives/353-An-Example-Zend-Framework-Blog-Application-Part-2-The-MVC-Application-Architecture.html Ryan Chan-2 wrote: > > what are the recommended way to make the > controller "thin"? > -- View this message in context: http://www.nabble.com/Split-controller-actions-into-multiple-classes-tp25508838p25530137.html Sent from the Zend Framework mailing list archive at Nabble.com.
