Nope, what you're doing makes complete sense. The purpose of the controller is to act as the "glue" between the model and the view. The controller can also aggregate and operate on other types of data as well, and for some of the logic, you need data outside the model, i.e. session data, so it makes sense that that logic would go in the controller.
But if you have any other logic that can be completely contained within the model, by all means, put it there. That's what the object is there for. As always, use common sense. The most important things to remember about the principles that Cake enforces is to maintain separation between the tiers of MVC (most importantly between view and controller), and most importantly, Don't Repeat Yourself. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
