"... and they're more or less in the right order. ..." Not really. But thank you for the nice reply. The issue here is that my understanding is no better with your explanation.
It is curious that the introductory explanation for beginners is full of specialized and undefined jargon. As is usual with any new technology, one who wants to learn it must learn the jargon. And so, I will learn the jargon. But... With my limited understanding of the process, I have re-written the above paragraph, without the jargon. There are three levels to MVC, the "Model", the "View" and the "Controller". An HTTP request message is received the Controller, which sends the message to an internal handler. The handler translates the message from HTTP to a format compatible with the Model and sends the message to the Model. The Model applies business processes to the message, such as database read, update and delete, and generates any appropriate reply message. The reply message is then passed to the View module. The View module formats the reply message into HTML for the user's browser, and transmits the reply message to the user. There!!! See? No jargon. The jargon can be defined later, in the tutorial. I hope that my explanation is "correct", not having used the MVC model. Instead I use the three tier programming model. If the paragraph is correct, you might consider replacing the current paragraph. thanks Joe On Mon, Sep 19, 2016 at 6:55 PM, Dave Newton <davelnew...@gmail.com> wrote: > On Mon, Sep 19, 2016 at 4:09 PM, Joseph B Cotton <cott...@gmail.com> > wrote: > > > What is meant by "mediated", > > > "Form a connected link between" > > > > "tied" > > > "Attached" > > > > "adapter" > > > "Connector between differing functionality" > > > > ? (I am a native English > > speaker, with years of programming experience including Java.) > > > > Hm. > > > > What is the difference between "represents" and "encapsulates"? These > very > > different terms are uses seemingly as synonyms. > > > > See next. > > > > "business logic and state" - again "logic" and "state" are very different > > concepts. Used here as synonyms. > > > > No, they're used as intended: either business logic *or* state *and, since > we use "or", possible both) are represented (and encapsulated) by a model. > > (Noting that neither is actually mandatory in the handler, but there is *a* > model represented by an action. It may or may not be the "final" model in a > modeling chain.) > > "Forwarded back" - oxymoron. > > > > Vaguely, especially if pedantry is present. > > > > "Loose coupling" - oxymoron. > > > > Most certainly not; "loosely coupled" is a ubiquitous term in software > engineering. > > And, last but not least, "make applications significantly easier" - in the > > category of "to boldly go" i.e. split infinitive. > > > > Ah, the "split infinitive". If this were written in Latin, this would be a > much livelier discussion. It's English, though, and even the > heavily-prescriptive Elements of Style does not say not to split them. So > if you are (or were) an English teacher, holding the split infinitive up as > something that's "wrong" wouldn't hold water. It holds less water since > this isn't an English class. > > He knows what he wants to say, but what he says is not what he intends, > > apparently. > > > > I'd disagree. There might be minor tweaks (when isn't there?) but the words > used have fairly well-known meanings in both the technical and > English-speaking community, and they're more or less in the right order. > > Dave > > -- > e: davelnew...@gmail.com > m: 908-380-8699 > s: davelnewton_skype > t: @dave_newton <https://twitter.com/dave_newton> > b: Bucky Bits <http://buckybits.blogspot.com/> > g: davelnewton <https://github.com/davelnewton> > so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton> >
