News for hackers. Stuff that matters.

A comment on How Not to write a "REST" API. Parent comment

Re:How Not to write a "REST" API by stevejalim on Wednesday February 01, 2012 @11:51AM (#3538747)
If you're learning about REST, do it right and make this book your bible - it's brilliant: http://www.amazon.com/Restful-Web-Services-Leonard-Richardso...
[ Parent | on HN ]
Re:How Not to write a "REST" API by dlokshin on Wednesday February 01, 2012 @12:19PM (#3538898)
Correct link: http://www.amazon.com/Restful-Web-Services-Leonard-Richardso...
[ Parent | on HN ]
Re:How Not to write a "REST" API by stevejalim on Thursday February 02, 2012 @04:27AM (#3542056)
Whoops, sorry!
[ Parent | on HN ]
Re:How Not to write a "REST" API by danellis on Wednesday February 01, 2012 @02:51PM (#3539587)
Why should that particular book be the bible? I haven't read it, but I've flicked through it and seeing things like the suggestion that clients should "construct" URLs made me doubt its worth.

Shouldn't Fielding's original thesis be the bible?

[ Parent | on HN ]
Re:How Not to write a "REST" API by stevejalim on Thursday February 02, 2012 @04:29AM (#3542057)
Ok, maybe bible was used to loosely. In my experience, I found it a well written, well balanced, useful primer for real-world development of RESTful web services that also has enough depth to make it a reference I've returned to since. That's better.
[ Parent | on HN ]