Sonic Baker: I guess I was kind of loose in that other posting about my definition of business logic. Business logic to me is what RUNS the show. The manager (controller) is what runs the show. That doesn't mean that model (Regional Manager) doesn't enforce their own logic. Good that we went back to the key DRY. As long as you are ahdering to that you should be fine. I just didn't want you to be sititng struggling for hours trying to figure out how to move all code into the models and have the controllers only callling a bunch of methods.
I must admit that I probably have used a protected action in a controller when I should have put it in the model. Chris: I just redid my application to remove a lot of the confusion from my controllers. I am calling more methods in my controller and it is controlling and the model is doing more data manipulation. Just now I thought of code I have replicated between two actions that I can place in the model. I just tend to forget that you can still use associated model calls in the models. It isn't limited to the controller since I used to overuse the $uses array. So to help me keep things simple I have cut WAY down on the uses array, placed code that is used more than one in the model. This has simplified my controllers and made the logic of what happens much easier to follow. Nice post. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
