Página InicialGruposDiscussãoMaisZeitgeist
Pesquisar O Sítio Web
Este sítio web usa «cookies» para fornecer os seus serviços, para melhorar o desempenho, para analítica e (se não estiver autenticado) para publicidade. Ao usar o LibraryThing está a reconhecer que leu e compreende os nossos Termos de Serviço e Política de Privacidade. A sua utilização deste sítio e serviços está sujeita a essas políticas e termos.

Resultados dos Livros Google

Carregue numa fotografia para ir para os Livros Google.

RESTful Web Services por Leonard Richardson
A carregar...

RESTful Web Services (edição 2007)

por Leonard Richardson

MembrosCríticasPopularidadeAvaliação médiaDiscussões
427457,809 (3.82)Nenhum(a)
""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… (mais)
Membro:biblab
Título:RESTful Web Services
Autores:Leonard Richardson
Informação:O'Reilly Media, Inc. (2007), Paperback, 446 pages
Coleções:A sua biblioteca
Avaliação:
Etiquetas:biblab, teknisk, web services

Informação Sobre a Obra

RESTful Web Services por Leonard Richardson

Adicionado recentemente porsynshop, nomssi, gbooch, JSyed, extantproject, nillacat
Nenhum(a)
A carregar...

Adira ao LibraryThing para descobrir se irá gostar deste livro.

Ainda não há conversas na Discussão sobre este livro.

Mostrando 4 de 4
What a waste of time. The entire book reads like a frustrated high school debater saying, "You're right, but I still think it would be better if I was right instead."

Richardson & Ruby "coin" the term Resource Oriented Architectures, by pointing out that it is actually a term previous used by a 2004 paper from James Snell, but they don't like the way he defined it so they are going to abscond with it and rework it.

They give very little insight into the possible benefits of their style of RESTful services, instead they spend a lot of time deriding "Big Style" web services, RESTful-RPC hybids, and other non-pure systems.

What I found really enlightening is how much the authors struggled to find successful RESTful examples. Everything from flickr, to Google, to del.icio.us, to Amazon have been doing it wrong and at best, the authors explain, are only half-assing it with RESTful-RPC.

All that tells me is that either the authors are the smartest guys in the world and can see what some of the web's best engineers cannot; or, REST simply isn't that compelling.

The book also simply is a failure at explaining what REST is and isn't. They make confusing and arbitrary delineations between one design decisions being RESTful and another not.

For example:
http://www.somesite.com/rest-service?method=search&q=penguins
and
http://www.somesite.com/rest-services/search?q=penguins

The first one, not RESTful, second one yes. The authors explain that the method should be the HTTP method: GET, PUT, POST, DELETE, etc.

The second URI invokes GET on the resource /search and passes some "scoping" information as "q=penguins." So for the search we can a scope of penguins.

I say that the first is the same. You invoke GET on /rest-service and pass a scope of ?method=search&q=penguins. At some point you are just going to get into semantics, especially once you get past trivial search examples.

They do similar fudging with RESTful services need to be stateless., but they use examples that must have some idea of who is doing them. If you pass the sessionID as a URI param, ok, as a cookie, you are not RESTful. Which makes sense in terms of caching servers, but on write operations, why do you want to cache?

The whole book is about proselytizing REST, usually by denouncing the false religions. It does not offer the reader a new set of skills and an honest discussion of what REST is good for and when should look elsewhere. There is not good discussion of the limitations of REST.

What do I do when the data I need to pass in exceeds the 1024 limit of a URL? What if I would want to create a set of simple atomic methods, but I have clients that would like to make coarse grain calls by bundling many requests into one call? What if I would like to allow clients to pipe these bundles request together. And what is the difference between the buzz phrase "Javascript on Demand (JoD)" and all that other JS that I just fetched from the web. ( )
  lucasmcgregor | Jul 22, 2009 |
After creating a significant number of web services, I've come to appreciate standards that more closely resemble the web.

Any time I have to use XML-RPC, I have to use libraries that are (at best) not totally standardized. Unlike HTTP, HTML, and JSON which are much closer to a working consensus. ( )
  dvf1976 | Apr 24, 2008 |
The interesting part is the beginning clearly defining what's exactly a RESTful services. Some good points expressed regarding the simplicity of HTTP (the genius part of HTTP). The rest of the book is for the Ruby fan... ( )
  adulau | Aug 13, 2007 |
Interesting, but sloppy. ~100 pages in and it seems that every other page has an error or typo or contradiction or some other oddity.

I tend to trust the authors to get the essential concepts right, but the editing and tech review was so half-assed that the results are distracting. ( )
  jamesbritt | Jul 5, 2007 |
Mostrando 4 de 4
sem críticas | adicionar uma crítica

» Adicionar outros autores (4 possíveis)

Nome do autorPapelTipo de autorObra?Estado
Leonard Richardsonautor principaltodas as ediçõescalculado
Ruby, Samautor principaltodas as ediçõesconfirmado
Hansson, David HeinemeierPrefácioautor secundáriotodas as ediçõesconfirmado
Tem de autenticar-se para poder editar dados do Conhecimento Comum.
Para mais ajuda veja a página de ajuda do Conhecimento Comum.
Título canónico
Título original
Títulos alternativos
Data da publicação original
Pessoas/Personagens
Locais importantes
Acontecimentos importantes
Filmes relacionados
Epígrafe
Dedicatória
Primeiras palavras
Citações
Últimas palavras
Nota de desambiguação
Editores da Editora
Autores de citações elogiosas (normalmente na contracapa do livro)
Língua original
DDC/MDS canónico
LCC Canónico

Referências a esta obra em recursos externos.

Wikipédia em inglês (5)

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

Não foram encontradas descrições de bibliotecas.

Descrição do livro
Resumo Haiku

Autor LibraryThing

Leonard Richardson é um Autor LibraryThing, um autor que lista a sua biblioteca pessoal no LibraryThing.

página de perfil | página de autor

Current Discussions

Nenhum(a)

Capas populares

Ligações Rápidas

Avaliação

Média: (3.82)
0.5
1 1
1.5
2 1
2.5
3 13
3.5 6
4 25
4.5
5 11

 

Acerca | Contacto | LibraryThing.com | Privacidade/Termos | Ajuda/Perguntas Frequentes | Blogue | Loja | APIs | TinyCat | Bibliotecas Legadas | Primeiros Críticos | Conhecimento Comum | 201,809,819 livros! | Barra de topo: Sempre visível