- Taschenbuch: 446 Seiten
- Verlag: O'Reilly & Associates; Auflage: 1 (22. Mai 2007)
- Sprache: Englisch
- ISBN-10: 0596529260
- ISBN-13: 978-0596529260
- Größe und/oder Gewicht: 17,8 x 2,3 x 23,3 cm
- Durchschnittliche Kundenbewertung: 3 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 73.024 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
RESTful Web Services (Englisch) Taschenbuch – 22. Mai 2007
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
"Every developer working with the Web needs to read this book." - David Heinemeier Hansson, creator of the Rails framework. ""RESTful Web Services" finally provides a practical roadmap for constructing services that embrace the Web, instead of trying to route around it." - Adam Trachtenberg, PHP author and "EBay Web Services Evangelist". You've built web sites that can be used by humans. But can you also build web sites that are usable by machines? That's where the future lies, and that's what "RESTful Web Services" shows you how to do. The World Wide Web is the most popular distributed application in history, and Web services and mashups have turned it into a powerful distributed computing platform. But today's web service technologies have lost sight of the simplicity that made the Web successful. They don't work like the Web, and they're missing out on its advantages. This book puts the "Web" back into web services. It shows how you can connect to the programmable web with the technologies you already use every day. The key is REST, the architectural style that drives the Web.This book: emphasizes the power of basic Web technologies - the HTTP application protocol, the URI naming standard, and the XML markup language; introduces the Resource-Oriented Architecture (ROA), a common-sense set of rules for designing RESTful web services; Shows how a RESTful design is simpler, more versatile, and more scalable than a design based on Remote Procedure Calls (RPC); and includes real-world examples of RESTful web services, like Amazon's Simple Storage Service and the Atom Publishing Protocol; discusses web service clients for popular programming languages. It also shows you how to implement RESTful services in three popular frameworks - Ruby on Rails, Restlet (for Java), and Django (for Python), and focuses on practical issues such as: how to design and implement RESTful web services and clients. This is the first book that applies the REST design philosophy to real web services. It sets down the best practices you need to make your design a success, and the techniques you need to turn your design into working code. You can harness the power of the Web for programmable applications: you just have to work with the Web instead of against it.This book shows you how.
Über den Autor und weitere Mitwirkende
Leonard Richardson has been programming since he was eight. Recently the quality of his code has improved somewhat. He is responsible for libraries in many languages, including Rubyful Soup. A California native, he now works in New York. He maintains a website at http://www.crummy.com/. Sam Ruby takes a perverse pleasure in integrating disparate things. He is a Vice President of the Apache Software Foundation, chairman of the Jakarta project, member of the XML PMC. He is an officer of ECMA and convener of the TC39 group standardizing the CLI for DotNet. He is a member of the PHP group, and developer on the Apache Soap and Bean Scripting Framework projects. He is currently employed by IBM.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
I bought this book and it gave me everything I needed. A deep understanding of why to design my Web service restful as well as clear instructions how to practically implement them.
Anybody who needs to design as restful Web service will be happy to have this book.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
While this is all good and useful stuff, it also scatters the books focus, which eventually turns out to be its major problem. The topic orientation simply sucks. I would recommend reading the book in this order:
* Core knowledge
- Introduction, Chapter 1 and 3
- Chapter 4, 8, 9
- Optional: chap 10 (comparison to SOAP).
* REST service examples
- Chapter 5, 6 and 7
* REST clients
- Chapter 2 and 11
The service examples (chapter 5 - 7) should really have been one chapter. The client chapters does not show how to write clients against the provided example services, which is a major mistake. The core knowledge scattered throughout chapter 4, 8 and 9 (like the ATOM publishing protocol which is covered multiple places) should be collected and ordered.
So why the four starts ?. I have to admit that my annoyance with the books topical layout is trumped by the authors knowledge and their ability to pack a surprising number of usable facts into this book. So if you do not loose your way in their topical jungle then you will eventually come through as a REST maven.
I'm still glad I read it but found the blabbing rather frustrating. My 2c.
2) The authors frequently make best practices statements without actually supporting them with evidence or otherwise explaining what makes them best practices.
3) There's really only about 100 pages of content. The other three quarters of the book is repetition. For example, chapters 4 and 8 seem to be the same. There is even a specific example regarding content language that is presented in chapter 4 and not referred to but simply repeated in chapter 8.
This book could be obsoleted by a brief 3 part tutorial perhaps combined with a half-hour slide show.
It's also troubling that the authors have found it necessary to redefine already well defined industry terms and definitions in order to bolster their own arguments for REST. For instance the authors, throughout the book, repeatedly refer to all SOAP exchanges as being RPC like, which is certainly not the case. The authors make no attempt to compare and contrast real message-oriented or document-literal web-services against RESTful web-services. Chapter 10 includes one single sentence on "new WSDL features" like document/literal, which the authors admit to not covering, as encouraging the creation of RPC style web-services. At best this is simple ignorance and at worst is willful deception.
I'd recommend this book as a good resource on the idea of what it means for a web-service to be truly RESTful, but I would also advise the reader to approach this work from a critical thinking standpoint. It's obvious from reading this work that the author's have an agenda and that they are willing to alter industry standard terms and definitions in order to promote their work.
The problem I have with this book is that maybe there's too much information. REST is supposed to simplify things, right? Up until this point I've read about REST in a couple of Rails book. I understand it (I think) and believe it's the wave of the future, especially after spending hours slogging through 800+ page books on JEE Web Services, WS-Death-*s (good call DHH!) and SOAs. While this book clocks in with less pages, it's still a tough read at times. And sometimes it was easy to lose sight of the forest while meandering through the numerous and sometimes-scattered trees.
Maybe that's just how tech books are; I don't know. I do know that most people are pressed for time and don't live and breath this stuff - which could explain the popularity of the "For Dummies" and "Head First" series.
Come to think of it, that's what I'd like to see: a "Head First RESTful Web Services" book. I think that would actually *help more people* to understand, and thus use, this technology.