Home > Article > Backend Development > PHP MVC pattern (1)_PHP tutorial
PHP MVC pattern (1)_PHP tutorial
- WBOYOriginal
- 2016-07-13 10:27:34802browse
PHP Advanced Programming Study Notes 2014.06.18
MVC (Model-View-Controller, Model-View-Controller) is a very common design pattern that can simplify application development and maintenance. It logically separates the application into parts. The model part is responsible for the business logic of the application, encapsulates the methods of accessing the database and provides a reusable class library. The view section controls the appearance of the data and provides a mechanism for collecting data from the user. The controller part is responsible for connecting all matters, collecting data from views, and determining the execution logic of the program. Call the model's mechanism and parse the returned data, then submit the data to the view for display to the client. There are five shutdown factors to consider when choosing the right framework: architecture, documentation, community, support, and flexibility.
Typical workflow based on MVC
The designer creates a static, separate prototype design based on the existing business requirements and the functions to be implemented by the application. Then, it’s handed over to developers for review. The developer is responsible for ensuring that all required functionality is feasible. If the developer does not find any problems, they create a development plan, including the API model, which is then handed over to the integrator (responsible for the controller layer). If there is a problem with the prototype, the project is returned to the designer and the cycle continues.
Once the prototype and API model are ready, the integration work begins. The integrator will work on the prototype design, convert it into a template language, and integrate the design into the site URL structure. Then write a controller, a component that proxies requests between the WEB server and the model information they need to manipulate. After the results are generated, the view is fetched and output, and the controller provides data for all dynamic content.
Finally, once the API model is fully implemented, the application can be handed over to testers. If the model developers strictly adhere to the API to write code, and the integrator writes the controller according to the specification, then the testing work will go smoothly.
MVC Application
Application entry, MVC site usually implements a core script used to handle all requests on the WEB site. This file is called a boot file. The boot file is responsible for initializing the framework, including automatic loading of classes, reading configuration, parsing URLs to models, filling and encapsulating request information, initializing controller programs and other operations.
After booting is complete, the front-end controller will be instantiated and take over the running of the program. The front-end controller class is a built-in class responsible for interpreting request variables. It routes user requests to a method on the action controller. This method is called an action, and the action is responsible for implementing all functions. In this method, the model class will be instantiated, the view template will be parsed, and the results will be output.
Models generally do not follow any specific structure, but exist in a common location, so they may be loaded automatically by the framework. Models are tool classes that provide the required data manipulation and parsing capabilities.
Views are templates and can be written in any template language. The purpose of a view is not to contain any kind of processing logic or data manipulation in the view, and only output the data provided by the controller. The choice of template language (such as FastTemplate/Smarty) depends on whether it can be integrated with the target framework.