CSC/ECE 517 Fall 2009/wiki1b 13 za
History and Applications of the MVC Pattern
MVC - the buzz term!
MVC (Model-View-Controller) offers a framework consisting of a Model that enforces the logical rules that should be applied to the data. A View is pertaining to the user-interface. It helps the user to interact with the Model. Finally the Controller acts as the point of communication between the Model and the View, taking inputs or requests from the user and manipulating or processing the underlying data accordingly to provide the user with the desired outputs. For example, in an e-commerce business setting, a model will make sure that the shipping charges are correctly applied, a view will generate pages displaying the items available and a controller will make sure to add selected products to the cart of the customer.
MVC offers a clear separation of the presentation logic from the business logic. This is the main reason, why it has been a widely used architecture for web-based applications. With an MVC framework, it becomes easy to accommodate future changes and implementations in design or code. MVC pattern gained prominence because of its clean modular approach that allow programmers to follow a well-defined framework for implementing business or enterprise level applications. Though, it is worth mentioning that using the MVC methodology for designing applications requires a lot of planning in terms of working out the separations in design and the interactions between the various modules. What is achieved by keeping these functionalities separate is reusability which is one of the major advantages of MVC.
Evolution of MVC
MVC Architecture
Over all these years, history of MVC architecture has become dim. MVC was first modeled at Xerox PARC in the 70's. Trygve Reenskaug was the one who wrote original notes on MVC in 1978 but he never got to publish them. His first note on the MVC pattern consisted of : Model, View, Controller and Editor. The 'Editor' is a short-lived component that the 'View' creates when necessary. This component is created as an interface between the 'View' and the input devices. After Reenskaug left Xerox PARC, Jim Althoff with a group of other people implemented a version of MVC specific to the Smalltalk-80 class library [1]. Even though they changed his implementation and removed the 'Editor' , Trygve Reenskaug was credited for his work.
MVP Architecture
After the implementation of Smalltalk-80 MVC, there were a few downsides to MVC approach and so a new variant of MVC was introduced - MVP (Model View Presenter). It was very similar to MVC controller. The only difference was in the way the presenter was linked to the associated views. But over time, the difference got more obscure and now implementations of MVC frameworks follow more concepts of MVP [2].
MVC Design Pattern
Ward Cunningham and Ken Beck who were working with Smalltalk were the first to start the MVC design pattern in 1987. The MVC design pattern is different from the MVC architectural pattern. In fact there are many other design patterns - Analysis, Creational, Structural, Behavioral [3]]. More information on the use of MVC as an architectural pattern or a design pattern can be found at [4]
Comparison of the MVC implementations in various web-based frameworks
MVC being a framework can be exploited to work with various languages. A list of such languages would include C++, JAVA, Ruby, Flex, DOT NET and many more [Ref [5]]. We make an attempt here to compare the different implementations of MVC, with respect to the different programming and markup languages. But all the implementations of MVC fall into three categories: Oringinal MVC framework, Model 2 MVC framework and Web application framework.
Original MVC
The original MVC pattern is very simple and has a very different path for the data, request and response of the user. Here the Controller modifies the Model accordingly but does not interact with Views. The Views are updated directly by the Model. When the Model changes during an event, an observer design pattern is implemented to change the View in response to the event. Thus the View is continuously observing the Model, and gets updated.
This original pattern helps in Separated Presentation. According to Martin Fowler, Separated Presentation means "Ensure that any code that manipulates presentation only manipulates presentation, pushing all domain and data source logic into clearly separated areas of the program". [6]
Original MVC Model is very simple to understand and implement. It was the early approach for web-application development but is still used for simple applications. It is used for quick development. But the relation between View, Model and Controller, makes it difficult for different teams to work on it. Thus even though implementation is easy, work can not be divided.
Not many web-based frameworks use this approach. JavaServer Pages (JSP) uses this approach. This approach is also called page-centric approach. Here we only build JSP pages which interact with users and handle In the Model 1 approach to creating a JSP application, browser requests are handled by a JavaServer Page directly. These pages only send the request further for processing. These pages go ahead and display the dynamic content generated [7].
Model 2 MVC Framework
Most of the web-based implementations follow this version of the MVC framework. The MVC framework is now considered synonymous with this model. In this model, there is no more contact between 'Model' and 'View'. Everything happens with the 'Controller' at the center. Controller is responsible for co-ordinating the tasks within the application.
Whenever a request arrives it goes to Controller first, then it passes the data to Model for validation and processing. Then if the Model needs to pass some data back to the View, it does so, through the Controller, which invokes the View.
Model 2 MVC framework helps you to create complex applications easily. This approach is used for web-based applications that need to be modified regularly and maintained for a long time. This approach helps in application development, as View and Controller are so distinct, that they can be worked on, by different teams. And with a simple View, the designing team can do wonders without affecting the Controller. [8]
Model 2 MVC framework has been greatly appreciated by the industry. In Python, frameworks like Django [9] have used it. And, of course, in the ASP.NET world, frameworks like ASP.NET MVC [10], Maverick .NET [11] etc have used it.
There are many frameworks in Ruby which implement MVC. Some of them are Monkeybars, Camping, Nitro, and Ruby on Rails etc. Ruby on Rails is the most widely know MVC framework pattern and will be easy to understand due to our previous background.[12]. Ruby on Rails provides special features to implement MVC framework. It enables you to create the MVC file structure easily. It is divided into separate packages that get included by the Model, View and Controller files automatically, to connect the functionalities of these files.
- Model (ActiveRecord) : The ActiveRecord package maintains all the library functions which are required for binding the interface (i.e. object) and database. It also helps in handling validation, association, transactions, and more. Inclusion of this package enables Model to implement its functions.
- View (ActionView) : The ActionView package implements Embedded Ruby(ERb) based system. These help to define templates for data presentation. By including this library, the view files can use scripting languages like JSP, ASP, and PHP to display data. It also helps to integrate AJAX technology with these files.
- Controller (ActionController): The ActionController package is included in a controller file by default when it is created. This gives default controller behavior to it. It helps to organize the data by searching and sorting so that the view does not have any calculations to perform. ActionController package acts like a bridge between ActiveRecord (the database interface) and ActionView (the presentation engine).
Thus ActionController and ActionView provide facilities for displaying the data and ActionRecord provides techniques for manipulating the database.
Web Application Framework
After the Model 2 MVC framework became popular, it was enhanced further for its use, specific to enterprise-based web applications. JAVA, PHP, Flex tools and the like became highly popular with their applications in web development. These technologies came up with their own MVC frameworks. A few well-known web application MVC frameworks are Struts and Spring (JAVA based), Cairngorm (Flex), Symfony Framework (PHP). All these frameworks are typically based on MVC Model 2, but have added a rich set of features and unit-testing that facilitate easy maintenance of the web-application.
Struts from Apache is a an open source MVC based framework for creating JAVA applications [13]
The framework provides three key components:
- There is a central configuration file struts-config.xml that holds together the model, view and controller.
- Controller: The controller is a Servlet called as ActionServlet.
- View: Typically involves using JSP pages.
Requests from the client are sent to the controller in the form of "Actions" defined in the configuration file; if the controller receives such a request it calls the corresponding Action class that interacts with the application-specific model code. The model code returns an "ActionForward", a string telling the controller that output page needs to be sent to the client. Information is passed between model and view in the form of special JavaBeans. A powerful custom tag library allows it to read and write the content of these beans from the presentation layer without the need for any embedded Java code. [14]
References
http://heim.ifi.uio.no/~trygver/themes/mvc/mvc-index.html http://www.typo3-media.com/blog/mvc-mvp-typo3-introduction.html http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29 http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller#Implementations_of_MVC_as_web-based_frameworks http://www.martinfowler.com/eaaDev/uiArchs.html http://tutorials.beginners.co.uk/professional-jsp-architecture-part-4-the-page-centric-approach.htm http://stephenwalther.com/blog/archive/2008/08/24/the-evolution-of-mvc.aspx http://en.wikipedia.org/wiki/Django_web_framework http://en.wikipedia.org/wiki/ASP.NET_MVC_Framework http://en.wikipedia.org/wiki/Maverick.NET http://www.tutorialspoint.com/ruby-on-rails/rails-framework.htm http://struts.apache.org/ http://en.wikipedia.org/wiki/Apache_Struts