No validating saxparser implementation available
Note that while we provide as much of the media content as we are able via free download, we are sometimes limited by licensing restrictions.
Please direct any questions or concerns to The world of web services has been on a fast track to supernova ever since the architect astronauts spotted another meme to rocket out of pragmatism and into the universe of enterprises. A renaissance of HTTP appreciation is building and, under the banner of REST, shows a credible alternative to what the merchants of complexity are trying to ram down everyone’s throats; a simple set of principles that every day developers can use to connect applications in a style native to the Web.
We also take popular services that fall short of RESTfulness, like the us social bookmarking API, and rehabilitate them.
Why are we so obsessed with the Web that we think it can do everything? The web is certainly the most-hyped part of the Internet, despite the fact that HTTP is not the most popular Internet protocol.
You connected to the server, gave it the path to a document, and then the server sent you the contents of that document. It looked like a featureless rip-off of more sophisticated file transfer protocols like FTP. With tongue only slightly in cheek we can say that HTTP is uniquely well suited to distributed Internet applications because it has no features to speak of. In a twist straight out of a kung-fu movie,: the two basic design decisions that made HTTP an improvement on its rivals, and that keep it scalable up to today’s mega-sites.
Many of the features lacking in HTTP 0.9 have since turned out to be unnecessary or counterproductive. Most of the rest were implemented in the 1.0 and 1.1 revisions of the protocol.
The problem is, most of today’s “web services” have nothing to do with the Web.
We know such services can scale to enormous size, because they already do. What is it but a remote service for querying a massive database and getting back a formatted response?
We don’t normally think of web sites as “services,” because that’s programming talk and a web site’s ultimate client is a human, but services are what they are. You can harness this power for programmable applications if you work with the Web instead of against it, if you don’t bury its unique power under layers of abstraction.
We also show you the view from the client side: how you can write programs to consume RESTful services.
Our examples include real-world RESTful services like Amazon’s Simple Storage Service (S3), the various incarnations of the Atom Publishing Protocol, and Google Maps.
Search for no validating saxparser implementation available:
Supplemental files and examples for this book can be found at