thinkphp multi-layer MVC usage analysis

This article mainly introduces the usage of thinkphp multi-layer MVC, and analyzes the specific principles and related usage skills of multi-layer MVC in thinkPHP with examples. Friends in need can refer to it

This article describes the usage of thinkphp multi-layer MVC with examples. Share it with everyone for your reference, the details are as follows:

ThinkPHP supports multi-layer design.

1. Model layer Model

Use multi-layer directory structure and naming convention to design multi-layer model. For example, in project design, if you need to distinguish different model layers such as data layer, logic layer, service layer, etc., you can add them in the module Create Model, Logic, and Service directories under the directory, and divide all model operations on the user table into three layers.

1.Model/UserModel is used to define data-related automatic verification, automatic completion and data access interfaces

2.Logic/UserLogical is used to define user-related business logic

3.Service/UserService is used to define users Relevant service interfaces

These three models all inherit the Model class. For example, the data layer Home/Model/UserModel.class.php

namespace Home\Model;
use Think\Model;
class UserModel extends Model{}

Logic layer Home/Logic/UserLogical.class.php

namespace Home\Logic;
use Think\Model;
class UserLogic extends Model{}

Service layer Home/Service/UserService.class.php

namespace Home\Service;
use Think\Model;
class UserService extends Model{}

You can use the built-in D method or M method to call when calling

D('User') //实例化UserModel
D('User','Logic') //实例化UserLogic
D('User','Service') //实例化UserService

Call the default model layer Model There is no second parameter model file name when downloading the data access interface class. The default model layer is Model. You can also change the settings as follows:

The code is as follows:

'DEFAULT_M_LAYER' =>  'Logic', // 更改默认的模型层名称为Logic

In this case, the instantiation method needs to be corresponding Modified

D('User') //实例化UserLogic
D('User','Model') //实例化UserModel
D('User','Service') //实例化UserService

You can see that using D('User') will instantiate the UserLogice class by default. This is very flexible. If we verify data, automatic completion is completed in js. The data retrieval is done from the service interface, so there is only one Service layer and other layers are not needed.

2. View layer View

The view layer is composed of templates and template engines. A common third-party template is .tpl. You can use php code directly in the template. Multiple layers of views can simply use directories (template themes) ) to distinguish, for example:

View/default/User/add.html
View/blue/User/add.html

A more complex multi-layer view can also be distinguished using different view directories, for example:

view normal View layer directory
Mobile access the view layer directory

In this way, different templates can use different page styles, and you can also default the view directory, as follows:

The code is as follows:

'DEFAULT_V_LAYER' => 'Mobile', // 默认的视图层名称更改为Mobile

3. Controller layer Controller

ThinkPHP controllers have two categories, one is the core controller and the other is the business controller. The core controller is in the ThinkPHP directory, such as thinkphpThinkPHPLibraryThinkControllerHproseController.class.php, which is responsible for the scheduling control of the application, including the interception of HTTP requests. , forwarding, loading configuration, etc. What we are going to discuss here is the business controller, which is completed by the user-defined controller class. The implementation principle of multi-layer business controller is similar to the layering of the model, such as business controller and event controller,

Controller/UserController //用于用户的业务逻辑控制和调度
Event/UserEvent //用于用户的事件响应操作

Event has not been used yet. It looks very high-end. There are very few user events in web development, and most of them are completed in js.

Access controller Home/Controller/UserController.class.php is defined as follows:

namespace Home\Controller;
use Think\Controller;
class UserController extends Controller{
}

Event controller Home/Event/UserEvent.class.php is defined as follows:

namespace Home\Event;
use Think\Controller;
class UserEvent extends Controller{
}

UserContrlller is responsible for external Interactive response, response through URL request, such as http://www.php.cn/, UserEvent is responsible for internal event response and can only call A('User','Event') internally; similarly we can set the default controller Layer:

The code is as follows:

'DEFAULT_C_LAYER' => 'Event', // 默认的控制器层名称改为Event

The inside and outside are isolated. Multi-layer controllers are not mandatory. They can be layered freely according to the needs of the application. Different layered models can be called in the controller as needed. , you can also display different hierarchical views to implement different themes.

In the three layers of MVC, ThinkPHP does not rely on M and V. It can only have C or only V. The user only needs to define the view, and it can automatically recognize it without C. However, this weird writing method will make many Programmers who have just started are very confused.

Multi-layer design has not been used in the current project, but I have seen it a lot in .net projects. I will add more next time it is used.