RESTful Web Services Cookbook (Anglais) Broché – 23 mars 2010
|Neuf à partir de||Occasion à partir de|
Produits fréquemment achetés ensemble
Les clients ayant acheté cet article ont également acheté
Descriptions du produit
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Détails sur le produit
En savoir plus sur les auteursDécouvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.
Dans ce livre(En savoir plus)
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Meilleurs commentaires des clients
Commentaires client les plus utiles sur Amazon.com (beta)
Compared to my previous readings on REST, this book strongly emphasizes the use of consistent XML formats. For me, this was the most important lesson in the book. It is not enough to just use PUT and DELETE: in order to really think in terms of "representations," you need to design meaningful XML. Along these lines, Allamaraju's discussion of the Atom protocol is particularly interesting.
Picking this book up after a recommendation from an HN reader, I got 4 chapters in before the smoke cleared in my brain and I had multiple "Ah ha!" moments such that the whole concept cleared up for me in a matter of days.
It could be the writing style or presentation, but I just found it really easy to digest and answering all my questions as they popped up in my head.
An excellent resource for anyone else working on RESTful API design.
There is also some good information on presenting resources that are not nouns, nouns are easy right you have a collection of people for example, you want to list all the people and do CRUD operations on a particular person. This to me is classical rest and is strait forward to do, but what about verbs (not in the POST, DELETE http sense) but in the give me driving directions sense. The book covers this and actually uses driving directions as it's example.
There are a couple of issues I'm still trying to find covered in the book, like how to do pagination on a collection of resources correctly. There is at least one recipe on this, but I did not see how to indicate a default page size (ie I requested all user accounts, but only returned first 200 dues to size, how does the client know that 200 were returned)
The other thing is the proper way to use http get parameters in search and other limiting operations. It would be nice to have some basic recipes there, but to be fair I might just not have seen them yet.
All in all it's a nice addition to your technical library.
The main focus is on the architecture and concepts, not the specific implementation details for any different language. Truly a book outlining the foundations for a lasting technology.
If you are looking for a book telling you how to implement REST in Java or C# or Ruby or any other language, this is not the book you are looking for.