From what I understand, the MVC pattern works like this:
You have a Model, a View and a Controller (duh!)
* The Controller is responsible for user inputs and for updating the model based on these inputs;
* Once a method on the controller is called, the model gets changed and the Views registered are notified by the model (observer pattern);
* The Views updates themselves to reflect the new model;
Cake MVC model doesn't adhere strictly to this paradigm, right?
From what I can see, the main purpose of Cake's MVC is to separate things, but you can't for example register Views on a model and the model doesn't automatically notifies the Views.
Just a moment of ispiration as I go through my research on design patterns and their implementations :)
Thanks in advance,
Marcelo.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
