HTTP web services are programmatic ways of sending and receiving data from remote servers using
the operations of HTTP directly. If you want to get data from the server, use a straight HTTP GET; if you want to
send new data to the server, use HTTP POST. (Some more advanced HTTP web service APIs also define ways of
modifying existing data and deleting data, using HTTP PUT and HTTP DELETE.) In other words, the "verbs" built
into the HTTP protocol (GET, POST, PUT, and DELETE) map directly to application−level operations for receiving,
sending, modifying, and deleting data.
The main advantage of this approach is simplicity, and its simplicity has proven popular with a lot of different sites.
Data −− usually XML data −− can be built and stored statically, or generated dynamically by a server−side script, and
all major languages include an HTTP library for downloading it. Debugging is also easier, because you can load up
the web service in any web browser and see the raw data. Modern browsers will even nicely format and pretty−print
XML data for you, to allow you to quickly navigate through it.
Examples of pure XML−over−HTTP web services:
• Amazon API (http://www.amazon.com/webservices) allows you to retrieve product information from the
Amazon.com online store.
• National Weather Service (http://www.nws.noaa.gov/alerts/) (United States) and Hong Kong Observatory
(http://demo.xml.weather.gov.hk/) (Hong Kong) offer weather alerts as a web service.
• Atom API (http://atomenabled.org/) for managing web−based content.
• Syndicated feeds (http://syndic8.com/) from weblogs and news sites bring you up−to−the−minute news from
a variety of sites.
the operations of HTTP directly. If you want to get data from the server, use a straight HTTP GET; if you want to
send new data to the server, use HTTP POST. (Some more advanced HTTP web service APIs also define ways of
modifying existing data and deleting data, using HTTP PUT and HTTP DELETE.) In other words, the "verbs" built
into the HTTP protocol (GET, POST, PUT, and DELETE) map directly to application−level operations for receiving,
sending, modifying, and deleting data.
The main advantage of this approach is simplicity, and its simplicity has proven popular with a lot of different sites.
Data −− usually XML data −− can be built and stored statically, or generated dynamically by a server−side script, and
all major languages include an HTTP library for downloading it. Debugging is also easier, because you can load up
the web service in any web browser and see the raw data. Modern browsers will even nicely format and pretty−print
XML data for you, to allow you to quickly navigate through it.
Examples of pure XML−over−HTTP web services:
• Amazon API (http://www.amazon.com/webservices) allows you to retrieve product information from the
Amazon.com online store.
• National Weather Service (http://www.nws.noaa.gov/alerts/) (United States) and Hong Kong Observatory
(http://demo.xml.weather.gov.hk/) (Hong Kong) offer weather alerts as a web service.
• Atom API (http://atomenabled.org/) for managing web−based content.
• Syndicated feeds (http://syndic8.com/) from weblogs and news sites bring you up−to−the−minute news from
a variety of sites.
Comments
Post a Comment
https://gengwg.blogspot.com/