An experience in learning a year ago, still remained.
Sender: HAX (Hai Yan), News District: WebDevelop
Title: Re: MVC corresponds to WEBE
Sending station: Drinking water Source (July 11, 2002 19:49 Thursday), station letter
I have continued to watch today and have some new discovery.
[In the masterpiece of HAX (Hai Wei):]
: I have seen an article down today today:
: Objects and the Web
: Alan Knight, Naci Dai (this name seems to be Chinese name!)
The Web hierarchical framework is mentioned:
: INPUT corresponds to Input Controller in MVC
: Application Logic corresponds to Application Controller
: Business Logic corresponds to Model
: Presentation corresponds to View
Traditional MVC originated from the language of SMALLTALK for software development. But we have smaltalk
I don't know, many otherholds also think of MVC, and there is an absolute (deceit) MVC's tendency,
But today I repeated the picture in the objects and the web article, it is said to be in MVC.
Controller is just the control of Keyboard, Mouse, that is, INPUT Controller,
And the object of Input Controller on the web is obviously not the keyboard, but the HTTP's request
(So it seems that I have a familiar with SMALLTALK complaining that this MVC is different from the STUCTS.) ...
Moreover, more importantly, the original MVC is not obviously distinguished from Application Logic.
Business logic! Think carefully, SmallTalk is the college-style programming, I am afraid there is no
The concept of middleware.
Ask comrades, consciously distinguish Application Logic when learning programming.
Business logic? I guess the demand for multiple reuse and build complex applications.
Will you have a conscious Application Logic and Business Logic's division!
: I feel that I haven't made it clear about this correspondence. The main problem is
: Some confused with Business logic for Application Logic. because
: There is also a constitting of Content-Logic-Style. In fact, now understand, complicated
: Style also includes Presentation Logic, and Content-Logic's integration is
: There is a difference in the division of Model-Controller. Because for traditional web
: It only can understand the content without design Model! Of course this judgment is not
Yes: it is absolute. Because Content (Data) has become an independent layer, it will have
: Some models, but this model is usually not OO in MVC, general
: May be only structured and semi-structured data, or like Er Model. Obvious
: If this is the case, Business logic cannot be encapsulated to the object itself.
So it is easy to confuse the Controller (Application Logic)!
There is a bit not clear here, and Content-Logic and Model-Controller are different.
But there are similar problems. The former problem is Application Logic and Business Logic
Mixing the Logic layer (I judge the reason is Content lack of OO expression), the latter problem is
Application Logic and Business Logic are mixed into the Model layer (or rather rather than the layers of Application and Business).
: But there is a question, is it wrong with the content of the web?
: Is the mVC hierarchical to WeBE? I have no answer yet, but I tend to
: Model for non-traditional OOs (such as RDF) is required on the web.
Finally, OO seems to have a closedness ... but this idea is still very unclear.
Welcome everyone to discuss.
-
Do the system lack of assets, do the lack of communication, do the missing classification,
Do the lack of the project, do the lack of system, and make a team lack organization ...
※ Source: · Drinking water Source bbs.sjtu.edu.cn · [from: 202.120.15.34]
