CakePHP web application framework model
MVC Model
1.The browser makes a request to web server by request URL.
2.The web server (Apache, WEBrick, etc.) receives the request. It uses routes to find out which controller to use: the default route pattern is “/controller/action/id” as defined in configuration file. The web server then uses the dispatcher to create a new controller, call the action and pass the parameters.
3.Controllers do the work of parsing user requests, data submissions, cookies, sessions and the “browser stuff”.
4.Models are PHP classes. They talk to the database, store and validate data, perform the business logic and otherwise do the heavy lifting.
5.Views are what the user sees: HTML, CSS, XML, Javascript, JSON. They’re the sales rep putting up flyers and collecting surveys, at the manager’s direction. Views are merely puppets reading what the controller gives them. They don’t know what happens in the back room.
6.The controller returns the response body (HTML, XML, etc.) & metadata (caching headers, redirects) to the server. The server combines the raw data into a proper HTTP response and sends it to the user.