struct2.1 notes 01:MVC Framework thought shallow understanding

1.

struts 1, the world's first MVC framework released by Craig McClanahan in 2001, was embraced by Java Web developers around the world, and after 6 years of tempering, struts The 1 framework is more mature and stable, and the performance is well guaranteed. So far, Struts 1 is still the most widely used MVC framework in the world.

At present, the Web-based MVC framework is very numerous and develops quickly, with a new MVC framework being released every once in a while, such as JSF, Tapestry, and spring MVC. In addition to these well-known MVC frameworks, there are also some edge team MVC frameworks that can be used for reference.

For the enterprise to actually use the MVC framework, the stability of the framework should be the most important problem to consider. A newly-started framework may have some hidden problems in itself that will introduce its own bugs into its own applications. This is why I do not recommend the developer to implement the framework itself.

While struts 2 claims to be a completely new framework, this is only relative to struts 1. Struts 2 does have a lot of revolutionary improvements compared to struts 1, but it's not a new framework for new releases, but rather a development based on another prestigious framework: WebWork. To some extent, Strut2 did not inherit the lineage of struts 1, but inherited the lineage of webwork. Alternatively, webwork derived struts 2, instead of struts 1 derived from struts 2. because struts 2 is a webwork upgrade, not a whole new framework, it is well-guaranteed in terms of stability, performance and so on, and it absorbs the advantages of struts 1 and webwork, so it's a very good framework to look forward to.

2.

MVC Brief:

  view includes a web design live template design that provides a mechanism for collecting data from users. The controller merges the view design with the model, is responsible for collecting data from the view, and determines the execution logic of the program calls the model layer and parses the return data so that it can be displayed at the view level.   
   
 
        3.        
 
       mvc thought shallow understanding:        
     

First of all to understand what is mvc,m (model), V (view view), C (Controller controllers), the idea of MVC is to divide an application into three parts, MVC, three parts that work together with minimal coupling to improve the scalability and maintainability of the application, (Achieve high cohesion, low coupling, the coupling between modules depends on the complexity of the interface between modules, the method of invocation and the information passed).

A model can correspond to multiple views, whereas multiple views can correspond to a model.

The concept of controller control layer is also very effective, because it combines different models and different views to complete different requests, therefore, the control layer can be said to contain the concept of user request permission.

If the user does not make a request to the app, the view cannot actively update itself.

struct2.1 notes 01:MVC Framework thought shallow understanding