What is the use of the MVC development model for??
MVC is a design pattern that makes it mandatory to separate the input, processing, and output of an application. Using an MVC application is divided into three core parts: model, view, controller. Each of them handles their own tasks.
Is it necessary for us to strictly distinguish between MVC's three-layer mode mode? Cross-border use of M and C is more conducive to rapid development.
In the framework I use, M and C can be used across borders, not strictly differentiated. Sometimes I would like to deal with M directly in C, because business data processing is not uncommon, perhaps only once. So I'm writing a function inside M,
The use of the C call, which is complicated, is inconsistent with the PHP rapid development concept.
What do we need?
1. View Detach
2. Code Reuse
3. Development efficiency
So I think in the MVC pattern development, do not have to force to distinguish between M and C, need to reuse the data into m, simple do not need to reuse can be thrown directly into C. What do you think??
The above describes the implementation of the private purchase of new energy vehicle subsidy pilot of the comments on the PHP MVC development model, including the introduction of private purchase of new energy car subsidy pilot of the content, I hope to be interested in PHP tutorial friends helpful.
