The standard practice as I understand it is Fat Models, Skinny Controllers.
Your business logic should go in the model. The basic rational is that if you include that logic in your model, then you can re-use it in any controller that uses that model... On Jun 20, 9:36 am, "Siebren Bakker" <[EMAIL PROTECTED]> wrote: > Pretty much all of the business logic for a cake application is supposed to > take place in the controller, as this is how MVC frameworks are designed to > work. This puts all of your logical code in one location, where it can > easily be found and modified. I've found that when adding new functions into > my controllers that alphabetizing the functions in the controller file, and > putting an extra newline between functions keeps my code readable, and > allows quick and relatively painless scrolling to the appropriate code. Your > controller does become large, but as long as you keep things organize, this > is not really an issue. > > In the name of Life, Liberty, and the pursuit of my sanity. > Siebren Bakker(Aevum Decessus) > > On Fri, Jun 20, 2008 at 00:48, SajjadRaza <[EMAIL PROTECTED]> wrote: > > > Hi > > i am novice to php and cake i have shifted from java and now in fix > > about lkayer distribution wher i ahev to put my businaess logic > > the suggested place is controller but by this my contrller becomes > > large > > can i put my logic in the model or some where else in the i want to > > work in the following layers > > view Controller businessLogic and model > > please guide me in theis regard > > > thanks > > zaidi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
