I am happy to announce that the RESTful Web Services Cookbook is now available in stores.
Many thanks to Mark Nottingham, Eben Hewitt, Colin Jack, Stefan Tilkov, Norbert Lindenberg, Chris Westin, Dan Theurer, Shaunak Kashyap, Larry Cable, Alan Dean, Surya Suravarapu, Jim D’Ambrosia, Randolph Kahle, Dhananjay Nene and Brian Sletten for their valuable and critical feedback on this book.
If you are interested reviewing the book, please email me directly. The Yahoo! Developer Network may be interested in publishing a review.
{ 10 comments… read them below or add one }
Congratulations on getting that finished.
congrats! feels good, doesn’t it?
Hi Subbu,
I’d like to review the book .
thank you,
BR,
~A
Congrats Subbu!
This looks like interesting material for the JavaZone conference in Oslo in September. Read more about how to submit an abstract here: http://jz10.java.no/program.html
I’m not sure if this is too late, but I too would like a review copy if that’s possible.
Waiting to hear from you.
Can’t wait to get my pre-ordered copy!
Hi Subbu,
Congratulations and thanks a lot for this great book.
One remark though: I’ve just read the chapter 14.1 on “How to Document RESTful Web Services” and I find it a bit contradictory to what you wrote some time ago on InfoQ (http://www.infoq.com/articles/subbu-allamaraju-rest). In this article, and I agree with you, you explain clearly that what is important is to document links, relations and media types instead of URIs. URIs are meant to be opaque and therefore not documented as is. But in this chapter 14.1, your advice is to document “All resources and methods supported for each resource”. To me, it looks similar to a context-free documentation of URIs. My understanding of a RESTful client is that it does not know what and where is the “Photo” resource, it should only know what HTTP methods apply to a link of a given relation in a given context and how to process a photo media type. I would be very interested to have your opinion on this subject.
Best regards,
-emmanuel
Good observation. Documenting resources and methods supported is still a good exercise since it can be handy when writing client code.
{ 2 trackbacks }