Skip to content

Technology of Web1.0 and Web2.0

August 12, 2009
tags:

The following figures illustrate the technology stacks of Web1.0 and Web2.0.

Technology stack of Web1.0
Technology stack of Web2.0
Browser
Application Client Container(ACC)
Unreliable HTTP
Internet Messaging Bus(IMB)
Application server
Mashup server

Examining the stack components:
Browser and Application Client Container(ACC):
ACC does not replace the browser whereas it is built on top of the browser.
1) ACC is stateful and browser is stateless. So in Web2.0 applications, a stateful application is built on top of the stateless browser.ACC is stateful because it supports asynchronous communication between the browser and server.
2) While standard browsing experiences are delivered by Web1.0 applications, a rich online user-experience is afforded by ACC.
From unreliable HTTP to Internet Messaging Bus (IMB):
As the internet was initially designed to share and view hyperlinked documents called webpages, the communication layer based on the HTTP REQUEST/RESPONSE model was sufficient for browsing. But in the Web2.0 stack we find a new component, the Internet Messaging Bus the main purpose of which is to provide enhanced web communication functions that go beyond the typical HTTP REQUEST/RESPONSE processing.IMB enables server push and message reliability, while still leveraging the standard HTTP protocol.IMB ensures that messages be reliably delivered just once and in the same order in which they are sent.
Let me now substantiate on the role played by IMB in Web2.0 applications.
Without IMB, if a user requests a page, it is quite unpredictable as to whether his request will arrive at the server or not due to frequent network problems. Of course it does not pose any problem as the user always has the advantage of clicking the URL twice or thrice even if the first URL request is lost. But in business transactions, such unreliability is often risky.
IMB also delivers messages in the order in which they are sent. Without IMB,if a user submits two requests in a row, there is no assurance as to which request will arrive first at the server. Again it is not a problem for browsing but for business transactions improper order of delivery of messages will lead to erratic behavior of the application.
Without IMB, a user request may arrive on the server more than once if owing to network problems the message was cached and delivered at the server. This will prove to be critical to business applications.
Hence IMB eliminates the above problems in Web2.0 applications by supporting server-initiated communications called Server Push while HTTP supports only Client Pull.
Server Push is a process in which the server maintains an open connection with the browser after the initial request for a page. Through this open connection the server continues to provide updated pages and content even though the visitor has made no further direct requests for such information. The server forces new versions of the document on the client at regular intervals while in client pull, the client initiates communication with the server. Forex. enterprise applications like stock trading require the server to push the latest stock prices to the end user.
From Application server to Mashup server:
Application Server is the middleware component in a web 1.0 stack.
A mashup combines data from more than one source into a single integrated tool. The Enterprise Mashup Server does not replace the application server, but instead, serves as an additional component to simplify the development and maintenance of composite applications.
An enterprise mashup server enables three tasks:
1. Data integration
2. Service/business process integration (logic integration)
3. UI integration
Advertisements
No comments yet

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: