I take your point, and I'll admit that my controllers are often too fat. I call model functions as much as possible, but find myself dipping back into the controller when I need to use the Auth component, the Session, redirect and so on (although I do collect as much info as I can and pass it into the model function when possible). Am I alone in that?
What is the principle behind fat model/skinny controller; is it performance, efficiency, code cleanliness? Jeremy Burns Class Outfit [email protected] http://www.classoutfit.com On 4 Feb 2011, at 09:09, AD7six wrote: > > > On Feb 4, 8:13 am, Jeremy Burns | Class Outfit > <[email protected]> wrote: >> Create a function in your controller that firstly creates the connection >> object. > > Holy MVC sacrilege batman. I hope you meant to say model. > > $stuff = $this->Model->somefunction() > > is about as far as a controller should go > > AD > > -- > Our newest site for the community: CakePHP Video Tutorials > http://tv.cakephp.org > Check out the new CakePHP Questions site http://ask.cakephp.org and help > others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > [email protected] For more options, visit this group at > http://groups.google.com/group/cake-php -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
