Ne hai uno da vendere?
Passa al retro Passa al fronte
Ascolta Riproduzione in corso... In pausa   Stai ascoltando un campione dell'edizione audio udibile.
Maggiori informazioni
Visualizza tutte le 2 immagini

RESTful Web Services (Inglese) Copertina flessibile – 22 mag 2007

3,9 su 5 stelle
5 stelle
31
4 stelle
22
3 stelle
7
2 stelle
3
1 stella
6
3,9 su 5 stelle 69 recensioni clienti su Amazon.com

Visualizza tutti i formati e le edizioni Nascondi altri formati ed edizioni
Prezzo Amazon
Nuovo a partire da Usato da
Copertina flessibile
"Ti preghiamo di riprovare"
EUR 27,34
click to open popover

Descrizione prodotto

Descrizione del libro

Web services for the real world

L'autore

Leonard Richardson (http://www.crummy.com/) is the author of the Ruby Cookbook (O'Reilly) and of several open source libraries, including Beautiful Soup. A California native, he currently lives in New York.

Sam Ruby is a prominent software developer who has made significant contributions to the many of the Apache Software Foundation's open source projects, and to the standardization of web feeds via his involvement with the Atom web feed standard and the popular Feed Validator web service.He currently holds a Senior Technical Staff Member position in the Emerging Technologies Group of IBM. He resides in Raleigh, North Carolina.

Non è necessario possedere un dispositivo Kindle. Scarica una delle app Kindle gratuite per iniziare a leggere i libri Kindle sul tuo smartphone, tablet e computer.

  • Apple
  • Android
  • Windows Phone

Per scaricare una app gratuita, inserisci il numero di cellulare.



Dettagli prodotto

Recensioni clienti

Non ci sono ancora recensioni di clienti su Amazon.it
5 stelle
4 stelle
3 stelle
2 stelle
1 stella

Le recensioni clienti più utili su Amazon.com (beta) (Potrebbero essere presenti recensioni del programma "Early Reviewer Rewards")

Amazon.com: 3.9 su 5 stelle 69 recensioni
2 di 2 persone hanno trovato utile la seguente recensione
5.0 su 5 stelle Wonderful book if you have complex and large data 24 giugno 2012
Di Amazon Customer - Pubblicato su Amazon.com
Formato: Copertina flessibile Acquisto verificato
PROS:
- Provides rigorous (and somewhat academic) description of RESTful-ness and Resource Oriented Architecture (ROA)
- Wonderful book if you have complex and large data
- This book is great for intended audiences:
-- web app/service architect/designers
-- who have complex / large data
-- who are looking to surface those data via web service and web applications
-- who think good organization is very very important (a little bit of OCD would help :)

CONs:
- Not wonderful book if you do not have complex and large data
- It would be boring or irrelevant for:
-- a reader who doesn't satisfy any of the above criteria

The authors are geniuses and have deep knowledge on the whole web space. They also have firm idea on how web-apps and web-services have to be designed to make the entire web better organized, while (almost succeeding in) not being a religious fanatic on the design principles. Hence their presentation is deep and insightful. It opens up your eyes on simple, yet overarching principles of web (HTTP, URI, ...) and teaches you how considering RESTful-ness would improve your web service / app architecture.

Like some geniuses, there writing style could be sometimes lengthy and pedantic, not compact. But their writing is still crisp and precise. Academic-degree preciseness. That may be why some are put off by this book but I view it as a small price to pay to learn from their wisdom.

I found this book while designing REST API to use for our existing web application. Our web-app is a niche player, but very large and complex system and I was looking to add REST API to make the whole system more "modern". I had some doubt about the book from reading some of negative reviews, but after I completed reading it (on kindle during 8-hour flight), I was sold. The book answered my short term questions, and something much, much bigger and fundamental: RESTful way of looking at web service and applications. It actually convinced me that our web-app could have been designed much better had we known of RESTful / ROA principles and applied them early on. I definitely will remember to re-read this book when our web app/service project comes along.
7 di 8 persone hanno trovato utile la seguente recensione
4.0 su 5 stelle Should be called RESTful Web Services for Ruby 24 giugno 2011
Di CW - Pubblicato su Amazon.com
Formato: Copertina flessibile Acquisto verificato
The author does a good job explaining most REST concepts that a developer would need to think about. The book is worth it for that alone. And, I am not aware of a better explanation out there.

I do think he could have covered more about what to do with large return data sets -- he briefly mentioned using a page arg in the query string, like google's search results uses, and returning "next" link in the response to help the client know how to get to the next page. But, he also says an Atom feed is a good way of providing lists of other resources, although an Atom feed doesn't provide a paging mechanism nor a way to link to the next page at the end of your current page. I wish he took these concepts further to suggest to the developer how he could provide paging of large returned data sets that you'd typically have with collections of a large number of resources of a particular type.

One thing he did not touch on at all was the disagreement out there on whether a PUT to an existing resource should always completely replace the entire resource, or modify just the properties of that resource that were sent in the body of the PUT, or some combination of both. I lean towards a PUT defaulting to replacing the entire resource (or failing if you're not allowed to replace a resource), and optionally using query string args to control how the existing resource is modified. If you look at the growing OSLC specifications, their strategy is to have query strings that say which properties are being updated for an existing resource.

And, if a PUT is updating an existing resource, you'd want to do a GET of it first, remember the ETag, then do a PUT while passing the header If-Match: <that-etag>. That helps deal with conflicts from simultaneous updates from multiple clients.

I also had some issues with his URI design choices for his fake "map" service. Map type and scale should not be part of the path; they are really more appropriate as part of the query string. The path is referring to the same map location regardless of the map type or scale.

And finally, the Ruby examples were very distracting and completely unnecessary. I don't know Ruby, so I found it painful trying to figure out what the strange-looking syntax was really doing. To explain REST, it is not necessary to give Ruby examples... it is sufficient to explain what the URI, headers, entity-body and HTTP return status code look like. Which, fortunately, he DID do, making his own examples unnecessary. Any good developer can readily write HTTP and XML code in the language he needs to use; it isn't that difficult. So, no need to focus on one language. I'd give it 5 stars except for this annoyance, so that's why I give it 4 stars.

I definitely recommend this book despite a few of the negatives.
1 di 1 persone hanno trovato utile la seguente recensione
3.0 su 5 stelle Easy to read and learn, but you'll have to weed through some filler. 3 agosto 2015
Di Megan - Pubblicato su Amazon.com
Formato: Copertina flessibile Acquisto verificato
As far as technical books go, this one is very well-voiced and easy to read and understand. However, there also seems to be a decent amount of filler sections thrown in just to make the book longer. It was helpful for learning REST, but I think it could have conveyed the same amount of useful information in a shorter book.
9 di 9 persone hanno trovato utile la seguente recensione
4.0 su 5 stelle Great (but repetitive) Guide 11 marzo 2008
Di J. Brutto - Pubblicato su Amazon.com
Formato: Copertina flessibile Acquisto verificato
Sure... it's got its issues: very repetitive, some glitches here & there... But overall, it's the best (if not the DEFINITIVE) guide to RESTful Web Services.

If you've used SOAP and/or other Web Services-related technologies/schemas/etc. etc. etc. you should have no problem following this. For beginners, however, it is definitely not the place to start. You will need to read-up a bit more on Web Services in general and some of the options and practices out there.

The repetition in the book isn't so bad. It drives home a lot of good points and covers quite a bit of in-depth information (sometimes too much, but it has come in handy when talking with other professionals/engineers).

To work with Web Services and not have at least glanced over this book would be a huge mistake. Just be careful: it may take you a while to get through. It does get a little boring from time to time.
4.0 su 5 stelle Fantastic starter book for REST and the design principles 25 dicembre 2016
Di CS - Pubblicato su Amazon.com
Formato: Copertina flessibile Acquisto verificato
Fantastic starter book for REST and the design principles. I don't agree on all the ideas presented in the work, but overall the concepts are solid (not a fan of parsing xhtml like Leonard uses in many of the examples). Would recommend :)