The similarities and differences between MVP and MVP

Answer 1

MVP (Model View Controller) and MV (Model View View Model) were both software architecture patterns. They had the following similarities and differences:

##1. Common Points
Both are designed to separate different aspects of the application for better organization, maintenance, and testability.

##2. Different Points
1. ** Communication Method **
- The communication between the various parts of MVP was one-way. The process was to send commands from View to Controller. After Controller completed the business logic, it asked Model to change the state. Model sent the new data to View, and the user received feedback.
- The communication between the various parts of the MV was two-way, and it used two-way data binding. The changes in the View were automatically reflected in the View Model, and vice versa.
2. ** Degree of logical separation between page and data **
- In MVP, the View could directly access the Model, so the View would contain Model information and some business logic. MVP did not really separate the page from the data logic.
- In concept, the real separation of the page and data logic mode, it put the data binding work into a file (such as a JS file) to achieve, the main function of this file is to complete the data binding, that is, to bind the model to the elements of the user interface.
3. ** Key architectural features and functions **
- MVP was a back-end development idea that moved data from the back-end through the controller layer to the front-end view. Model is the part of the application that deals with the data logic of the application (such as storing and retrieving data from the database);View is the part of the application that deals with the display of data;Controller is the part of the application that deals with user interaction. It receives requests and decides which model component to call to process the request, and then determines which view to use to display the returned data.
- The core of an architecture model based on front-end development was to provide two-way data binding between View and View Model. The View Model was responsible for connecting the View and Model to ensure the data and view were consistent. Model is the data object related to business logic;View is the user interface that is displayed; and View Model is the bridge connecting view and model, which can realize the two-way binding of data. When the data changes, View Model can monitor and automatically update the view. When the user operates the view, View Model can also monitor the change of the view and notify the data to make changes.
4. ** Maintaining and Reusable Code **
- In the MVP model, because some business logic was implemented in the View, it was difficult to change the View, and the business logic could not be reused.
- By putting some view logic into the View Model, many views could reuse this view logic. The View could be changed and modified independently of the Model. A View Model could be bound to different View.
5. ** Operation differences when data changes **
- In the MVP model, when the data of the Model changes, you may need to manually manipulate the Dom element to change the display of the View.
- When the data of the Model changes, the corresponding data will automatically change in the View layer.
Read more exciting novels for free