Register now or log in to join your professional community.
HTTP request comes to the controller then controller categorized an action, then send request to the Model to get data for the categorized action, then finally send the action to the view and process the view to send as a HTTP response. so the workflow is Controller-Model-View.
MVC does not represent a workflow. It is not meant to describe how data flows through the application, it is a statement of roles.
Controller knows about views and models. Views know about Models. Models just know about themselves. So hence the naming convention MVC
Usually the model is created first
MVC is a architecture or a pattern where the Model, View and the Controller are the main components.
It was introduced as MVC but it can be CMV, VCM, etc.
Well, seems the name might be related to the request/ response journey and the rendering process.
However, Please review the link I have visited during my search on this subject.
http://theartandscienceofruby.com/2016/07/05/why-is-it-called-mvc/
as i know the name did not put because of the workflow but because of the major role of the part
and at the end its just a name for software architectures introduced by Trygve Reenskaug into Smalltalk-76 while visiting the Xerox Palo Alto Research Center (PARC)in the 1970s , In the 1980s, Jim Althoff and others implemented a version of MVC for the Smalltalk-80 class library. Only later did a 1988 article in The Journal of Object Technology (JOT) express MVC as a general concept.
That what i think