Shulou(Shulou.com)06/02 Report--

This article mainly introduces what the mvc design pattern refers to, which can be used for reference by friends who need it. I hope you will learn a lot after reading this article. Next, let the editor take you to learn about it.

Mvc design pattern represents the page through JSP technology, completes a lot of transaction work through Servlet technology, and realizes the user's business logic. In this mode, Servlet is used to deal with the requested transaction and acts as a controller.

"MVC" mode is: "Model-View-Controller" mode. In this mode, the page is represented by JSP technology, and a large number of transaction work is completed by Servlet technology to realize the user's business logic.

In this mode, Servlet is used to handle the requested transaction and acts as the controller (Controller, "C"). Servlet is responsible for responding to the customer's request for business logic and deciding which JSP page to send to the customer according to the user's request behavior. The JSP page is in the presentation layer, that is, the role of the view (View, or "V"). JavaBean is responsible for data processing, that is, the role of the model (Model, i.e. "M").

Servlet+JSP+JavaBean (MVC) mode is suitable for the development of complex web applications. In this mode, servlet is responsible for handling user requests, jsp is responsible for data display, and javabean is responsible for encapsulating data. The layers between the modules of Servlet+JSP and JavaBean mode programs are clear, and this mode is recommended for web development.

MVC architecture

The Model-View-Controller architecture pattern was invented in the Smalltalk-80 GUI (a classic object-oriented programming language) laboratory in the mid-1980s.

According to the MVC model, a software should separate business logic (Model) from display (View). Separation has many advantages, the most important of which are two aspects:

1. The same business logic layer (Model) may correspond to multiple display layers (View). If the business logic layer and the display layer are put together, adding another display layer will greatly increase the complexity of the components. An example of business logic facing two display layers is that the business logic layer of a bank's account corresponds to the ATM and Internet display layers.

2. In general, there is no need to modify the business logic layer every time you modify the display layer.

Thank you for reading this article carefully. I hope the editor can share what the mvc design pattern refers to is helpful to everyone. At the same time, I also hope that you will support us, pay attention to the industry information channel, and find out if you encounter problems. Detailed solutions are waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.