Thanks Grant. Appreciate your thoughts. On 1/23/07, Grant Cox <[EMAIL PROTECTED]> wrote: > > Well, it is debatable. Since controllers are the users interface to > your application - what are the users trying to achieve? Are they > aware of Orders being separate to Practices, and will they want to > access methods specifically to Orders? If so, it should have its own > controller. > > If you have a model that is only used in the backend of the > application, and has a very limited interface, then I think it is ok > not to have a controller. But if it's just an object like any other > (albeit associated with others), then it is better code separation for > it to have its own controller, and public facing actions. > > > > >
-- "I never look back darling, it distracts from the now", Edna Mode (The Incredibles) --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
