Notes 25 - Web Services

Notes 25 - Web Services - Web Services and REST: Yahoo,...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
Copyright © Ellis Horowitz 2006-2010 1 Web Services and REST: Yahoo, Amazon, and Google
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Introduction Web sites are normally accessed by a user agent, e.g. a browser But we have seen that programs can also access a web site, return one or more pages, and scrape the site for information Web services is the idea of offering the capabilities/information on a web site via a programming interface, so application programs can more readily access the information on the site Web Services are APIs for accessing a website’s information across the Internet The implementation of Web Services are roughly divided into two categories: Big Web Services which involve XML messages that are communicated by the Simple Object Access Protocol (SOAP); the API is formally described using the Web Services Description Language (WSDL) Representational State Transfer (REST) services which use HTTP methods PUT, GET, POST and DELETE Copyright © Ellis Horowitz 2006-2010 2
Background image of page 2
Copyright © Ellis Horowitz 2006-2010 3 Web Services are Becoming Common Many web sites are now offering their facilities through web services Here are the URLs for the web services from Yahoo, Google, Amazon and Ebay http://developer.yahoo.com/everything.html , e.g. • Desktop widgets: code for developing widgets • Browser plus: a set of Javascript extensions http://code.google.com/apis/ajax/ • Google Maps Google AJAX Feed • Google AJAX Search Google Visualization • Google Earth Google Book Search http://aws.amazon.com/ Amazon Elastic Compute Cloud (Amazon EC2) • Amazon Elastic MapReduce • Amazon CloudFront • Amazon Fulfillment Web Service • Amazon Simple Storage Service http://developer.ebay.com/businessbenefits/aboutus/
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
REST (Representational State Transfer) REST is a style of software architecture for distributed hypermedia systems (i.e. The Web) – Initially proposed by Roy Fielding in a 2000 doctoral dissertation – The World Wide Web is an example of REST There are three fundamental aspects of the REST Design Pattern – 1. client, 2. servers and 3. resources • Resources are typically represented as documents • Systems that follow Fielding's REST principles are often referred to as RESTful ; Resources Every distinguishable entity is a resource URLs Every resource is uniquely identified by a URL Simple Operations (PUT,GET,POST,DELETE) 4 Copyright © Ellis Horowitz 2006-2010
Background image of page 4
REST versus Other Approaches REST – Software architectural style for distributed hypermedia systems like WWW – Quickly gained popularity through its simplicity SOAP – Protocol for exchanging XML-based message, normally using HTTP – Much more robust way to make requests, but more robust than most APIs need – More complicated to use XML-RPC – RPC protocol with XML as a encoding and HTTP as a transport – More complex than REST but simpler than SOAP
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 48

Notes 25 - Web Services - Web Services and REST: Yahoo,...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online