Model View Controller Frameworks for Mobile View Website

Model View Controller Frameworks for Mobile View Website

Copyright: © 2023 |Pages: 17
DOI: 10.4018/978-1-6684-8582-8.ch014
OnDemand:
(Individual Chapters)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

Websites have evolved over the past few years utilizing a variety of programming languages and frameworks. There were other developers working on them concurrently. Developers deploy their projects utilizing a number of design patterns to handle these sophisticated web apps, which makes the code simpler and easier to work with. They are well known for using the model view controller approach. Model, view, and controller, or MVC, are the three components that make up an application in accordance with the MVC architectural pattern. Each of these parts is made to address particular facets of application development. This chapter focuses on MVC for mobile device website viewing. The various sections of this chapter address the introduction to MVC, MVC components, the architecture pattern, several techniques used to implement the pattern in the project, and an example of MVC architecture. Towards the end of the chapter, the advantages and disadvantages of MVC are examined.
Chapter Preview
Top

The Mvc Pattern And Literature Overview

The MVC was invented by Trygve Reenskaug in 1978 or 1979, when he was visiting a scientist at Xerox Palo Alto Research Center (PARC). According to the first reports on MVC, it is named “Thing Model View Editor,” but it was quickly modified to “Model View Controller.”

The primary reason for creating MVC was to provide user control over complex data sets. The MVC practice evolved in response to time and demand. Because it was created before web browsers, the MVC pattern was initially used as an architectural pattern for graphical user interfaces (GUI). MVC is now used to create web applications. Ruby on Rails, Laravel, Zend Framework, CherryPy, Symphony, etc. are a few web frameworks that leverage the MVC idea (Dey, 2011).

The architecture that offers several views of the same data is known as the MVC design pattern. It splits the application objects into three classes: the Model class, the View class, and the Control class. It also distinguishes between the data layer and the expression layer. The business and data logic are handled by the Model class, the display logic by the View class, and the control processing by the Control class. Three different types of logic are used by MVC to create control and display logic-oriented applications, as well as business and data logic-oriented applications. The business and data logic are unaffected by the change in business processes. The model class is the only thing that changes when business concepts and algorithms change (Leff & Rayfield, 2001). In order to ensure the independence of the modules, MVC separates the data access and display.

A dynamic e-business system or an Internet application can be created and implemented using the MVC design pattern. The e-commerce market is expanding quickly, and the enterprise-level application is emerging quickly. As a result, an increasing number of initiatives at the enterprise level are following the trend of embracing Web technology as their primary technology. Middleware and other server-end technologies are becoming more and more important at the same time. Therefore, the enterprise's information technology department needs a workable strategy for creating the application and connecting it to that middleware, which is adaptable and portable.

Complete Chapter List

Search this Book:
Reset