1 / 14

Web 2.0.. Was there a Web 1.0?

Web 2.0.. Was there a Web 1.0?. Ramesh Loganathan. Hype?. When did you first hear of Web 2.0?. Is it real?. Can a new technology Gain real traction in few months?. How many of us here have heard of Web 1.0?. Old Web? New Web?.

vaughan
Download Presentation

Web 2.0.. Was there a Web 1.0?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web 2.0.. Was there a Web 1.0? Ramesh Loganathan

  2. Hype? When did you first hear of Web 2.0? Is it real? Can a new technology Gain real traction in few months? How many of us here have heard of Web 1.0?

  3. 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

  4. 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”:

  5. 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 Key Drivers

  6. 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 XMLWebserviceAPIs • Semantic Web (Tagging) • Some social networking aspects

  7. Different people.. Different strokes Enterprise Solutions Portals & Application Designers Solution Architects Bring SOA To the User (UI) Usability Engineer Fat clients- Better user exp Content Producers Focus more On backend services Simple Interactions. Refer Multiple sites Wide Consumer base SMB Software Developers Information Designer Software As a service Collated & Aggregated More Usage potential Online Services UI Designer Rich UI Simple, & rich, Solutions User Web 2.0

  8. Web 2.0- Big PIC XML over net Well known sites • 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 Amazon Flickr (tagging) Info Blogs & Info sites http Web 2.0- Client Search engine Wiki pedia Services Access Rich UI RSS http Flash? Google earth JS/AJAX Geo-spatial Data Handling http Aggregators Net/financial services XML AJAX E-Commerce SOAP eBay REST Media REST Bindings Banks Pay.t Gateway Audio/Video++ Web Services SOAP RSS BUILD Use Web 2.0 Portal Enterprise Services Infrastructure • Designed per Web 2.0.. • Access other net sites & services • Expose RSS, REST, ++ access

  9. Technologies in Web 2.0 XML over net Mashups Security Identity http Rich Client Access http RSS Services JS Maps User Application RSS SOAP REST Bindings Ajax Flash REST RSS SOAP The Web2.0 Application Enterprise Services Infrastructure • 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

  10. Anatomy of a Web 2.0 Application Client Web 2.0- Client APIs Rich UI Services Access UI Layouts Flash? JS/AJAX http Local “flows” AJAX JS components Access Resources Over net Local processing (JS) Data Handling Aggregators XML AJAX SOAP Load AJAX page Media REST Bindings Audio/Video++ RSS Web 2.0 Portal JSPs • Designed per Web 2.0.. • Access other net sites & services • Expose RSS, REST, ++ access App Navigation Struts Flow Control

  11. References

  12. Views?

  13. Thank You. http://jroller.com/page/rameshl rameshl@pramati.com

  14. Rich 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. Reference: Key Usage Areas

More Related