On Jul 19, 2:34 pm, Geoff Ford <[EMAIL PROTECTED]> wrote: > My personal opinion - one controller per 'type' of 'operation'. I > think all actions that can be performed on a single object (not > necessarily a single model) should be managed in the one controller. > Different permissions to those actions should be handled by ACL. > > I think different controllers for each role could get very messy, very > quick and lead to lots of duplicate code. >
Thanks for your reply. I think I do agree with you but now I wonder how should be driven the "names normalization". So, Cake samples define a model Product and a product_controller. Which is the best practice to call to a controller for logged user operations on a product ? (if that exists, obviously). Thanks in advance J --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
