I get emails whenever the latest "Methods and Tools" free PDF comes out, and they have an article about web development with Ruby on Rails in it this time around, so I thought I'd take a snippet from it where they discuss in Rails terms what they think the three parts of MVC mean:
"Model: the information the application works with, the model is usually persisted to a database but that is not necessary." "View: a representation of the model, multiple views are possible for one model, in fact that is one of the benefits of using an MVC pattern. In a Web application this is usually an HTML page but can also be Flash page or something else." "Controller: the controller defines what neesd to happen on different events, like the user clicking on a button, usually changes one or multiple models and chooses the correct view for the model." So, going by that set of definitions it's obvious to me that my practice of simple models and complicated controllers is not the "accepted paradigm" for MVC. Placing data validation and other data munging in the model seems to be the way of this definition. Food for thought, that's for sure. -- Chris Hartjes "The greatest inefficiencies come from solving problems you will never have." -- Rasmus Lerdorf @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
