TP framework 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. I hope to be helpful.

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 models. For example, in project design, if you need to distinguish between data layer and logic layer Different model layers such as layer and service layer can create Model, Logic, and Service directories under the module 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 user-related 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 layerHome/Logic/UserLogical.class.php

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

Service layerHome/Service/UserService.class.php

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

You can use the built-in D when calling Method or M method is called

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

There is no second step when calling the data access interface class under the default model layer Model Parameter model file name, the default model layer is Model, you can also change the settings as follows:

'DEFAULT_M_LAYER' => 'Logic', // Change the default model layer name to Logic

In this case, the instantiation method needs to be modified accordingly

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

You can see that using D('User') By default, the UserLogice class will be instantiated. This is very flexible. If we verify data, the automatic completion is done in js, and the data retrieval is done from the service interface. In this way, we only need one Service layer. The other layers are not needed.

2. View layer View

The view layer consists of templates and template engines. A common third-party template is .tpl. You can use php code directly in the template. Multi-layer views can be distinguished simply by using directories (template themes), for example:

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

More complex multi-layer views can also be distinguished by different view directories, for example:

view Normal View layer directory

mobile Access the view layer directory on mobile

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

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

3. Controller layerController

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 thinkphp\ThinkPHP\Library \Think\Controller\HproseController.class.php, responsible for application scheduling control, including interception, forwarding, loading configuration, etc. of HTTP requests. 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 This 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 interaction response, responding through URL request, such as http ://serverName/User/index, UserEvent is responsible for internal event response and can only call A('User','Event') internally; similarly we can set the default controller layer:

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

The interior and exterior are isolated, and 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, and different layered views can also be displayed to achieve Different themes.

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

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.

Related recommendations:

#TP5 Auth Permission Management Example

# #TP5 automatic loading mechanism detailed explanation

TP5 Model function summary

The above is the detailed content of TP framework multi-layer MVC usage analysis. For more information, please follow other related articles on the PHP Chinese website!