thinkphp的mvc（ThinkPHPs MVC）.docVIP

thinkphp的mvc（ThinkPHPs MVC） ThinkPHPs MVC Author: Sun Hongtao 2009-11-30 11:36 User rating: / 5 Bad ThinkPHPs MVC MVC is a design pattern that is mandatory to separate application input, processing, and output. Using MVC, applications are divided into three core components: model (M), view (V), and controller (C), each dealing with its own tasks. View: the view is the interface that the user sees and interacts with. For the old Web application, the view is composed of a HTML element in the new interface, Web application, HTML is still in the view plays an important role, but some new technology including Adobe Flash and they emerge in an endless stream, like XHTML, XML/XSL, WML and Web services and some other markup language. How to handle application interfaces is becoming more challenging. A big benefit of MVC is that it can handle many different views for your application. No real processing occurs in the view, whether the data is online storage or an employee list, and as a view, it is only a way to output data and allow the user to manipulate it. Model: the model represents enterprise data and business rules. Of the three components of MVC, the model has the most processing tasks. For example, it might use a component object like EJBs and ColdFusion Components to process the database. The data returned by the model is neutral, that is, the model is independent of the data format so that a model can provide data for multiple views. Because the code applied to the model can be reused by multiple views with only one write, the repeatability of the code is reduced. Controller: the controller accepts input from the user and invokes the model and view to complete the users requirements. So when you click the hyperlink in the Web page and send the HTML form, the controller itself doesnt output anything and do anything. It simply receives the request and decides which model component to call to process the request, then determines which view is used to display the mode