When I browsed the technical forum recently, I occasionally encountered several PO, VO topics that were popular with MVC and time. (http://forum.javaeye.com/viewtopic.php?t=627) Seeing that everyone is eager to speak, I also want to join in the fun. Unfortunately, this forum has been registered with 10 days to speak ... then let's write here. . .
I found that these posts are discussing vo is M or V. In fact, I don't think it is necessary. MVC model theory has such a background. It was a lot of applications at that time, putting the display, data storage, module definition, etc., all mixed in a module (page), causing such an application to be difficult to maintain and reuse. The proposal of the MVC theory is to make developers, noticed the application in this case. MVC is not very accurately defined when it is proposed. If you are looking for online, you will get a bunch of seemingly the same and less than a crazy explanation and definition. But I still have to define what he is here. According to the background mentioned above, I think the MVC proposed at the time. Just decompose the application simple safety.
C (Control) control, represents the control section (such as session bean), but I think the control is not just a certain class. He can refer to an IF statement, which can refer to a component, and should also refer to the business control process. M (Module) model, mode, this is the most blurred portion. According to my understanding, it is based on the business related or integral structure. For example, the overall business structure, a data structure, data dictionary, etc. V (view) view, indicating that the part is displayed directly to the user or directly interacting with the user.
The original intention of MVC is very good. Unfortunately, his definition is too blurred (or learners do not understand correctly, such as me:>), inability to compare. Leading, some of the application or framework of MVC is still many defects. In my opinion, MVC is not a hierarchical concept is his maximum cause.
After MVC, there is no formal proposal concept. However, I thought that the concept of developers now so-called multi-storey applications has exceeded the concept of the MVC model, although it derived from MVC model ideas. The concept of multi-layered applications is a hierarchical concept, although there is no clear definition now, but its implementation can quantify the relatively weak. The quantified scale is the fastening of the coupling between the hierarchy and the hierarchy. Also, the so-called hierarchy has "invasion" on other levels, as well as the degree of intrusion. . . (To be) (the above is purely personal)
