IntroductionMVC stands for Model-View-Controller. Model implies information, View implies representation and Controller implies business logic. MVC was originally depicted in terms of a design pattern for use with Smalltalk by Trygve Reenskaug in 1979. MVC could be a software architecture or we can say that MVC is a plan design or MVC may be a framework. The MVC pattern could be a process of breaking an application into three parts: the model, the view, and the controller. A Design pattern may be a code structure that allows common coding frameworks to be replicated rapidly. MVC is used in computer program development; the basic rule of MVC is based on the thought that the logic of an application and introduction are isolated from each other i.e. MVC is basically a much better way of isolating the logic of your application from the display. MVC is a design pattern which is used in software programming.
In MVC, the model speaks to data of the application; the view represents presentation logic and the controller represents all our business logic and oversees the communication of data and the business rules. The MVC design has been utilized in numerous programming languages and technologies such as Java, .NET and PHP etc. The purpose of the MVC pattern is to separate the model from the view so that changes to the view can be executed, or indeed additional views created, without having to refactor the model. A basic way to think of this would be to consider the following:
- • Model handles all our database logic.
- • Using the model, we interface to our database and give an abstraction layer.
- • A client interacts with the view - by clicking on a link or submitting a form
- • The View checks the state of the Model and reacts accordingly.
- • View speaks to our introduction logic i.e our HTML/XML/ code.
- • The Controller handles the client input, and exchanges the data to the model
- • The Model gets the data and updates it's state.
- • The Controller manages all our business logic i.e. all our ifs and else.
ModelModel is the first portion of the MVC design. Model handles all our database logic. The Model may not essentially have a persistent information store (database), but in case it does it may access it through a separate Data Access Object (DAO). The main features of a Model are as follows:
- • A model represents data e.g. a database table.
- • The model oversees the behavior and information of the application domain.
- • The model represents data and the business rules that govern access to and updates of this data.
- • The model is the piece of data that speaks to the state and low-level behavior of the component.
- • Model oversees the state. The model has no particular information of either its con-trollers or its views.
- • A model may have more than one view.
- • The view is the piece that oversees the display of the state represented by the model.
- • View represents our presentation logic i.e. our HTML/XML/ code.
- • A view is a kind of some form of visualization of the state of the model.
- • The view oversees the graphical and textual output.
- • It accesses enterprise information through the model and indicates how that information should be presented.
- • A view attaches to a model and renders its contents to the show surface.
- • The Controller represents all our business logic.
- • Using a controller we will alter the state of the model.
- • A Controller accepts input from the client and instructs the model and view to per-form actions based on that input.
- • The controller deciphers interactions with the view into activities to be performed by the model.
- • The Controller gives the mechanism by which changes are made to the state of the model.
- • The Controller handles the HTTP GET and POST requests.