Web 2.0.. Was there a Web 1.0?

Ramesh Loganathan

Hype?

How many of us here have heard of Web 1.0?

Can a new technologyGain real traction in few

months?

When did you first hear of Web 2.0?

Is it real?

Old Web? New Web?

• If lot of the current hot technologies have been around for some time..– Web Services API.. Around since 1998– Web Syndication- since 1997– AJAX- 1998– Services on the web (payment, information, ..) - 1990s– Blogs.. As web diaries/journals around for a long time– Online music around since mp3.com– Encyclopedias and information databases since Yahoo

& Britanica…

• Then what exactly is the next generation internet & Web 2.0?

Technology Uptake.. unpredictable

Web 2.0.. A marketing gimmick?

• It started with O’Reily pushing for discussions around the new possibilities around the Web

• Web as more than just “browse”:Web 1.0   Web 2.0

DoubleClick --> Google AdSense

Ofoto --> Flickr

Akamai --> BitTorrent

mp3.com --> Napster

Britannica Online --> Wikipedia

personal websites --> blogging

screen scraping --> web services

publishing --> participation

content management systems --> wikis

directories (taxonomy) --> tagging ("folksonomy")

stickiness --> syndication

Key Drivers

More than just technology..

• Easy availability of high Bandwidth

• Web based Services/ Payment gateways• Web based communities/ RSS & Syndication• Web based Applications• Deep penetration of blogs• Wikis .. more popular than simple web sites• Culture of looking for information from Blogs• Simple easy to access services

• Payment• Geo

• Household brands• Amazon, Google

Technologies at play

Recent developments & uptake on key constituents..• Unobtrusive Rich Internet Application techniques (such as

Ajax) • CSS • Semantically valid XHTML markup and/or the use of

Microformats • Advanced User Interface languages such as XUL and SVG • Flash Remoting • Syndication of data in RSS/Atom • Aggregation of RSS/Atom data • Clean and meaningful URLs • Weblog publishing • REST or XML Webservice APIs • Semantic Web (Tagging)• Some social networking aspects

Different people.. Different strokes

Web 2.0InformationDesigner Collated &

Aggregated

UsabilityEngineer

Simple Interactions. ReferMultiple sites

SolutionArchitects

Fat clients- Better user exp

EnterpriseSolutions

Bring SOATo the User (UI)

Portals &ApplicationDesigners

Focus moreOn backend services

ContentProducers

WideConsumer base

SMB Software

DevelopersSoftware As a service

OnlineServices

MoreUsage potentialUI

DesignerRich UI

User

Simple, & rich,Solutions

Web 2.0- Big PIC

RSS Bin

ding

sSOAP

REST

Enterprise Services Infrastructure

Search

engine

http

Blogs & Info sites

http

E-Commerce

REST

Google earth

RSS

Banks

SOAPWeb

Services

-Internet is the App platform-Use info sources from the web- Blogs, Serach Engines, et al-Use Geo/maps info-Use payment services-Access Enterprise services backbone

Aggregators

XMLovernet

Pay.tGateway

Services Accesshttp

Amazon

Rich UIFlash?

Data HandlingXML

MediaAudio/Video++

Net/financial services

Info

Geo-spatial

Web 2.0- Client

Well known sites

Flickr(tagging)

Wiki pedi

a

eBay

Web 2.0 Portal

• Designed per Web 2.0..• Access other net sites & services• Expose RSS, REST, ++ access

UseBUILD

AJAX

JS/AJAX

Technologies in Web 2.0

RSS Bin

ding

s

SOAP

REST

User

EnterpriseServices Infrastructure

RSS

http

REST

RSS

SOAP

-Can be end-user generic application-Can be enterprise app, that predominantly accesses the enterprise services. Occasionally accesses other internet based services such as blogs or say Google earth type resources

App

licat

ion

Aja

xServices

RichClient

Fla

sh

JS

Map

s

XMLovernet

Accesshttp

The Web2.0 Application

SecurityIdentity

Mashups

Anatomy of a Web 2.0 Application

RSS Bin

ding

s

SOAP

REST

Aggregators

Services Access

http

Rich UIFlash?

Data Handling

XML

MediaAudio/Video++

Web 2.0- Client APIs

Web 2.0 Portal • Designed per Web 2.0..• Access other net sites & services• Expose RSS, REST, ++ access

AJAX

JS/AJAXUI Layouts

AJAX JS components

StrutsFlow Control

JSPs

Load AJAX page

Local processing (JS)

Local “flows”

App Navigation

Client

AccessResourcesOvernet

References

Category Sites

Analysis & Trends Read/WriteWeb, Dion Hinchcliffe, Susan Mernit's Blog, Web 2.0 Explorer, /Message, Ben Barren

Companies & Products TechCrunch, SolutionWatch, eHub

Design & Usability WeBreakStuff, Bokardo, ParticleTree, Emily Chang

VC & Business Jeff Clavier, Nivi

Podcasting PodTech, Web 2.0 Show

Tech & Development Programmable Web, CrunchNotes, Librarystuff, Alex Barnett, Ajaxian

Commentary Scripting News, HorsePigCow, Scobleizer, Micro Persuasion

Mobile Open Gardens, MobileCrunch

Views?

Thank You.

http://jroller.com/page/rameshlrameshl@pramati.com

Reference: Key Usage AreasRich Internet Applications• Recently, Rich Internet Application techniques such as

Ajax have evolved that can improve the user experience in browser-based web applications. Ajax involves a web page requesting an update for some part of its content, and altering that part in the browser, without refreshing the whole page at the same time. There are proprietary implementations (as in Google Maps) and open forms that can utilise web service APIs, syndication feeds, or even screen scraping.

Server-side software• The functionality of Web 2.0 Rich Internet Applications

builds on the existing web server architecture, but puts much greater emphasis on back-end software. Syndication differs only nominally from dynamic content management publishing methods, but web services typically require much more robust database and workflow support, and become very similar to the traditional intranet functionality of an application server. Vendor approaches to date fall under either a universal server approach, which bundles most of the necessary functionality in a single server platform, or a web server plugin approach, which uses standard publishing tools enhanced with API interfaces and other tools. Regardless of the approach chosen, the evolutionary path toward Web 2.0 is not expected to be significantly altered by these choices.

Client-side software• The extra functionality provided by Web 2.0 depends on

users having more than passive access to the data on the servers. This can be through forms in an HTML page, a scripting language such as Javascript, or through Java. These methods all make use of the client computer to take varying degrees of work off the server.

Web protocols• Web communication protocols are a key element of

the Web 2.0 infrastructure. Two major ones are REST and SOAP. More recently, SOAP has dropped the acronym and is now only known as SOAP.

• REST (Representational State Transfer) indicates a way to access and manipulate data on a server using the HTTP verbs GET, POST, PUT, and DELETE.

• SOAP involves POSTing XML messages and requests to a server that may contain quite complex, but pre-defined, instructions for it to follow.

• In both cases, access to the service is defined by an API. Often this API is specific to the server, but standard web service APIs (for example, for posting to a blog) are also widely used. Most, but not all, communications with web services involve some form of XML (Extensible Markup Language).

• See also WSDL (Web Services Description Language), which is the standard way of publishing a SOAP API, and the list of Web service specifications for links to many other web service standards, including those many whose names begin 'WS-'.

RSS• Due to the recent development of these trends,

many of these protocols remain de facto rather than formal standards.