In weniger als einer Minute können Sie mit dem Lesen von RESTful Web Services auf Ihrem Kindle beginnen. Sie haben noch keinen Kindle? Hier kaufen.

An Ihren Kindle oder ein anderes Gerät senden

 
 
 

Kostenlos testen

Jetzt kostenlos reinlesen

An Ihren Kindle oder ein anderes Gerät senden

Lesen Sie Bücher auf Ihrem Computer oder auf anderen Mobilgeräten mit unseren GRATIS Kindle Lese-Apps.
RESTful Web Services
 
 

RESTful Web Services [Kindle Edition]

Leonard Richardson , Sam Ruby , David Heinemeier Hansson
5.0 von 5 Sternen  Alle Rezensionen anzeigen (1 Kundenrezension)

Digitaler Listenpreis: EUR 26,33 Was ist das?
Kindle-Preis: EUR 16,29 Inkl. MwSt. und kostenloser drahtloser Lieferung über Amazon Whispernet

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 16,29  
Taschenbuch EUR 24,95  

Kunden, die diesen Artikel gekauft haben, kauften auch


Produktbeschreibungen

Kurzbeschreibung

"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)
  • 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
  • Shows how to implement RESTful services in three popular frameworks -- Ruby on Rails, Restlet (for Java), and Django (for Python)
  • Focuses on practical issues: 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.

Synopsis

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


Produktinformation


Mehr über die Autoren

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


Tags

 (Was ist das?)
Bei einem Tag handelt es sich um ein Schlagwort, das zum Produkt passt.
Tags erleichtern allen Kunden die Suche und die Sortierung ihrer Lieblingsprodukte.
 

Kundenrezensionen

4 Sterne
0
3 Sterne
0
2 Sterne
0
1 Sterne
0
Die hilfreichsten Kundenrezensionen
4 von 19 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Das Buch namens RESTful Web Services ist zu empfehlen. Ich verstehe wie Web Services funktionieren, könnte aber nie verstehen warum viele Leute, die REST empfehlen, über Web Services schimften. Nach ich dieses Buch gelesen habe, habe ich verständnis bezüglich was REST ist und wie REST eingesetzt werden kann gewonnen. Das Buch behält auch sehr viel Informationen über HTTP und XML, sowie über Web Architekturen.
War diese Rezension für Sie hilfreich?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:  55 Rezensionen
69 von 71 Kunden fanden die folgende Rezension hilfreich
Brilliant and Horrible 19. Juli 2008
Von Lars Tackmann - Veröffentlicht auf Amazon.com
Format:Taschenbuch
Packed with all sorts of knowledge about REST, HTTP and AJAX this book will make you very capable at building well designed RESTful web services. Any topic imaginable is covered, from obscure ways of handling transactions, to Apache proxies, service implementations in Rails and the limitations of the current browser security model.

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.
72 von 76 Kunden fanden die folgende Rezension hilfreich
Good but pedantic and repetitious 29. August 2007
Von Alberto Accomazzi - Veröffentlicht auf Amazon.com
Format:Taschenbuch
Ok, the concept behind the book is valid: let's have computers use the web the way it was intended to be used, and if everybody sticks to a small set of reasonable design rules, we'd all be better off. But why does it take 400 pages for the authors to drive that point home (over and over again)? 70% of the content seems "filler" material, which has been put in just to turn this into a book. True, there are code examples that may be helpful to some beginner programmers, but I'm still left feeling that this could have been a well-written, 3-chapter book about 100 pages long.

I'm still glad I read it but found the blabbing rather frustrating. My 2c.
113 von 139 Kunden fanden die folgende Rezension hilfreich
Nearly Abysmal 2. August 2007
Von Evan Dower - Veröffentlicht auf Amazon.com
Format:Taschenbuch
1) The editors were apparently on vacation. There are numerous errors including several typographical errors that a simple spell-check would have caught (words like "ang" and "extrenal") and a number of ungrammatical sentences.
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.
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

Beliebte Markierungen

 (Was ist das?)
&quote;
The difference between PUT and POST is this: the client uses PUT when its in charge of deciding which URI the new resource should have. The client uses POST when the server is in charge of deciding which URI the new resource should have. &quote;
Markiert von 28 Kindle-Nutzern
&quote;
In RESTful architectures, the method information goes into the HTTP method. In Resource-Oriented Architectures, the scoping information goes into the URI. &quote;
Markiert von 16 Kindle-Nutzern
&quote;
A RESTful, resource-oriented service exposes a URI for every piece of data the client might want to operate on. &quote;
Markiert von 15 Kindle-Nutzern

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Thema:
Erster Beitrag:
Eingabe des Log-ins
 


Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   
Ähnliche Foren


Kunden, die diesen Artikel markiert haben, haben auch Folgendes markiert


Ähnliche Artikel finden


Anhand des Sachgebietes nach ähnlichen Produkten suchen: