Scribd
Upload
257 views

Pervasive Web Application Architecture

The document discusses pervasive web application architecture including its history, scalability, availability, and development. It describes supporting multiple devices and addressing problems of diversity. It covers ensuring scalability and availability through redundancy. It also discusses the MVC pattern and its application to pervasive computing, including different views for different devices.

Uploaded by

121Anik saha
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
257 views

Pervasive Web Application Architecture

The document discusses pervasive web application architecture including its history, scalability, availability, and development. It describes supporting multiple devices and addressing problems of diversity. It covers ensuring scalability and availability through redundancy. It also discusses the MVC pattern and its application to pervasive computing, including different views for different devices.

Uploaded by

121Anik saha
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 20

• Pervasive Web Application Architecture

– History
– Scalability
– Availability
– Development
– Application Architecture
• It support multiple devices, such as PCs,
WAP phones, PDAs and voice-only phones
enables to access web servers through voice
gateways.
• The architecture addresses the special
problems associated with pervasive
computing, including diversity of devices,
markup languages and authentication
methods.
History

• The problems that application programmers


initially faces when implementing web
applications with browser access from PCs
have, to a large degree, been resolved.
• Various technologies are available that
allow application programmers to create
transactional web applications in a
straightforward manner, supported by a
large number of tools.
• The advent of pervasive computing, application
programmers now face many new challenges.
– Users have many different devices that look and
behave in very different ways.
• Different user interfaces
• Different markup languages
• Communication protocols
• Authentication protocols
– Web applications that support pervasive computing
should adapt to whatever device their users are using.
– Application must provide in a form that is
appropriate for the user’s particular device – WML,
VoiceXML, HTML and so on.
– As a consequence, architectures for pervasive
computing application must not allow for
filtering of unnecessary information, and for
output targeted to different flows of interaction
depending on the user’s device.
– Another challenge that is posed by pervasive
computing is increased scalability and
performance requirements.
• The frequency of users accessing the application
from mobile phones will be higher than that of PC
users, as the phone always available.
• Pervasive computing web applications need to scale
to larger numbers of users than classical OC-only
web applications.
• Scalability
– Given the ever-growing number of pervasive
computing devices, scalability of pervasive
computing applications is a very important
issue.
– An example, large telecommunication
companies expect millions of users to subscribe
for some applications.
• Availability
– It is of particular importance in the pervasive
computing environment.
– For example, most users of pervasive
computing devices and applications will neither
understand nor accept comments like “server
currently down for maintenance” – if a
service is not available when they need it, they
will assume that it does not work, and will stop
using the application or switch to another
service provider.
• Both the scalability and availability issues
can be resolved by system topologies that
employ parallelism and redundancy.
Firewall Firewall

Authentication
Credential
WAP directory Server
Gateways
Authentication
Proxies
Voice
Gateways Back-end
Network Application
applications
dispatcher Server

PDA
Gateways Database
Network
Server
Demilitarized dispatcher
zone
Scalable topology for PCWA
• Development
– To implement web applications, four roles are
in a team as follows
• Business logic designers – functions and application
flow to be performed.
• User interface designers – responsible for look and
feel, and good usability.
• Application programmers – work with web
applications such as HTML, JSPs, etc.
• Experts for existing legacy database and transaction
systems – for implementing the application logic
and connectivity to database and transaction
systems in the back end.
– In addition to the above team a pervasive
computing specialist, who knows about the
capabilities of devices and the infrastructure
required to support pervasive computing
applications.
– For ex: WAP gateways, Voice gateways and
gateways for PDAs.
– Generally WML, and VoiceXML, which
normally cannot be handled well by traditional
web designers.
Pervasive application architecture

• The Model–View–Controller is a good


choice when implementing web
applications.
– The controller is implemented as a servlet.
– The model implemented as a set of EJBs.
– The views as JSPs.
• MVC
– The simplest way to implement Web
applications generating dynamic content is to
use JSPs that receive a request.
– It invoke application logic to perform the
required operations on the server side.
– Finally create and return and appropriate
response.

Request Application
Client JSP logic
Response
• Limitations with simple MVC
– It is too inflexible for real-life web applications.
– It does not provide appropriate separation of
responsibilities between Java programmers and
Web designers.
2.Execute Command 3.Access Model
1.Request Controller Model
Beans Ex: EJB

4. Pass request with


reference to
Client command bean

Views 5.Get result


6.Response Ex: JSP properties

The Web Application based on the MVC


MVC pattern applied to pervasive computing applications
Command
Bean - 1

Command
Bean - 2 Model-1

PC Command
Bean - 3 Model-2
Controller
Actio

Actio
Web
WAP Model-3
n

n
Application
(Server) Controller

Voice WAP View-1 Model-4


Controller

WAP View-2

PC View-1

Voice View
DB DB DB
Session

Application Application Application

Security
State Security Bean
State

Security Secure Content


Content
Policies access Delivery

Authentication
servlet
Device connectivity infrastructure

Secure pervasive architecture


Device specific authentication (servlet or web server)

PC PKI smart card authentication

WAP WIM authntication

Form-based authentication

5.Establish session
Form-based authentication (WML)

authentication
Session
6
3..Invoke

(2, 7) Check

9.Invoke application
1.Request
Proxy 10.Response
Application
11.Response
8.Check policy

Security
Policy
Form-based authentication with a WAP phone (first request)
Session
(2) Check

4.Invoke application
1.Request
Proxy Application
11.Response 5.Response

3. Check policy

Security
Policy

Form-based authentication with a WAP phone (subsequent requests)


• Secure MVC application
• Secure JSP application
• Interaction between the authentication
servlet and application servlet via the
session object
• Components used by the secure pervasive
access framework

You might also like