A Novel Web Application Frame
MVC Design Pattern MVC is a widely popular software design pattern , as early
as in the 70's, IBM introduced the Sanfronscisico on the project, in fact, is the
MVC design pattern research. Recently, with the maturity of J2EE, it is becoming
a recommendation in the J2EE platform , a design model , the majority of Java
developers are also very interested in the design model. MVC model is gradually
developed in PHP and ColdFusion are in use , and growth trends. With the rapid
increase in web applications, MVC model for the development of Web applications
is a very advanced design idea, no matter what language you choose, no matter
how complicated the application , it can be for you to understand and provide the
most basic application model analytical methods , structural products for you to
provide a clear framework for the design, for your software projects in accordance
with norms.
Abstract
The MVC (Model/View/Controller) design pattern was developed in Smalltalk-
80 and widely used in software design. This paper introduces a novel Web application
frame based on MVC. This frame separates the transaction logic from the presentation
format. It also improves the system maintainability, scalability and performance by
using the module database, template database, messaging object and buffer queue.
Key words: MVC, Design Pattern, Web Application
1. Introduction
Web application system is a transaction system based on B (rowser)/S(erver)
model. It exploits many kinds of dynamic Web developing technologies. At present,
Web application developing patterns and tools are one of the topics of the software
design. They directly influence several key factors such as maintainability, scalability,
stability and the security. In this paper, the purpose of MVC[1]-based Web application
design pattern is to resolve the two factors – maintainability and scalability, which are
the stubborn problems in the Web application development. By introducing the MVC
design pattern into the Web application development, the implementation of system
transaction logic can be separated from the system presentation.
MVC consists of three kinds of objects. 1) the Model: is the application object, 2)
the View: is its screen presentation, 3) the Controller: defines the way the user
interface reacts to user input. Before MVC, user interface designs tended to lump
these objects together. However, MVC decouples them to increase the flexibility and
reuse. MVC decouples views and models by establishing a “subscribe/notify”
protocol between them. A view must ensure that its appearance reflects the state of the
model correctly. Whenever the model’s data changes, the model notifies views that
depend on it. In response, each view gets an opportunity to update itself. This
approach lets you attach multiple views to a model to provide different presentations.
You can also create new views for a model without rewriting it.
2. Background and Problems
Even though the MVC design pattern was already put forward in smalltalk-80 and