-- josh.ribakoff <josh.ribak...@gmail.com> wrote (on Sunday, 20 September 2009, 03:00 PM -0700): > It depends, controllers are part of the presentation layer,
Umm, not really. Controllers take the request, and determine what view(s) and/or model(s) need to be instantiated. The view is the actual presentation layer. > if there is business logic it could be factored onto objects ( models > ) it belongs to. Yes, absolutely. > 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" Actually, repetitive presentation logic should be pushed into view partials or helpers, not action helpers. ;) > 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"? -- Matthew Weier O'Phinney Project Lead | matt...@zend.com Zend Framework | http://framework.zend.com/
