Home>Article>PHP Framework> What is MVC layering in thinkphp5
In thinkphp5, MVC layering refers to the division of labor and cooperation between the model layer, view layer and controller layer. The logic layer and presentation layer perform separate operations; the model layer is responsible for database operations, and the controller is a module class. , scheduled and operated according to the URL, and the view is used to connect the action controller and the template file.
The operating environment of this article: Windows 10 system, ThinkPHP version 5, Dell G3 computer.
MVC, M model, V view, C controller.
Layering means division of labor and cooperation, with the logical layer and the presentation layer operating separately. The model is responsible for: database operations. Controller: Any WEB operation is an operation of a module. The controller is a module class that schedules and operates according to the URL. View (composed of view class and template file): connects the action controller and the template file. The action class passes the data to the template file through the View class, and the template file converts the received data into the corresponding data format for display.
ThinkPHP is based on the MVC (Model-View-Controller, Model-View-Controller) pattern, and supports multi-layer (multi-Layer) design.
The default model layer is composed of the Model class, but as the project grows and the business system becomes more complex, it is difficult for a single model layer to meet the requirements. The design idea of Model support is very simple. Different model layers still inherit from the system's Model class, but they are distinguished in the directory structure and naming convention.
For example, in the design of a certain project, we need to distinguish between different model layers such as data layer, logic layer, and service layer. We can create model, logic, and service directories under the module directory to store all models in the user table. The operation is divided into three layers:
Data layer: model/User is used to define data-related automatic verification and automatic completion and data access interface
Logic layer: logic/User is used to define user-related Business logic
Service layer: service/User is used to define user-related service interfaces, etc.
And these three model operation classes can all inherit the \think\Model class.
The hierarchical division of model layers is very flexible. Developers can freely define and add model hierarchies according to the needs of the project. You can also only use the Model layer.
The view layer consists of a template and a template engine. PHP code can be used directly in the template. The design of the template engine will be described later. It can also support other functions through the driver. Third-party template engine. Multi-layer views can be simply distinguished by directories, for example:
view/default/user/add.html view/blue/user/add.html
More complex multi-layer views can be further implemented by using different view directories, for example:
view normal view Layer Directory
Mobile Access View Layer Directory
ThinkPHP’s controller layer consists of core controllers and business controllers. The core control The controller is completed by the App class inside the system and is responsible for the scheduling control of applications (including modules, controllers and operations), including HTTP request interception and forwarding, loading configuration, etc. The business controller is completed by a user-defined controller class. The implementation principle of multi-layer business controller is similar to the layering of models, such as business controller and event controller:
controller/User //用于用户的业务逻辑控制和调度 event/User //用于用户的事件响应操作
controller\User is responsible for external interaction response and responds through URL request, such as http://serverName /User/index, and event\User is responsible for internal event response and can only be called internally, so it is isolated from the outside. The division of multi-layer controllers is not mandatory and can be layered freely according to the needs of the application. In the controller layer, you can call the layered model as needed, or you can call different layered views.
Recommended learning: "PHP Video Tutorial"
The above is the detailed content of What is MVC layering in thinkphp5. For more information, please follow other related articles on the PHP Chinese website!