Table of Contents
- Preface
- 1. Using the Uniform Interface
- 2. Identifying Resources
- 3. Designing Representations
- 4. Designing URIs
- 5. Web Linking
- 6. Atom and AtomPub
- 7. Content Negotiation
- 8. Queries
- 9. Web Caching
- 10. Conditional Requests
- 11. Miscellaneous Writes
- 12. Security
- 13. Extensibility and Versioning
- 14. Enabling Discovery
- Appendix A. Additional Reading
- Appendix B. Overview of REST
- Appendix C. HTTP Methods
- Appendix D. Atom Syndication Format
- Appendix E. Link Relation Registry
{ 13 comments… read them below or add one }
What about security
Thanks,
Marco Parenzan
Yes. There is no book or blog that covers security aspect of RESTful web services. I wonder how REST works in case of statefulness? Certainly caching will not be possible.
I would love to see:
* How to prevent Request Throttling
* How to provide data protection, data Integrity & end user privacy
It will be great if you can provide a reviewer copy of your book? Certainly once the book is released I will purchase it
Regards,
Ramesh
Thanks for the suggestions. We will try to address those questions as well.
As we finish up the first draft of the book, we will try to get a draft out through O’Reilly’s Rough Cuts program. Please stay tuned.
Will these book also discuss about JSR311 JAX-RS?
For example showing how to use Jersey (https://jersey.dev.java.net) to quickly expose REST web service for your web application
We are trying to stay away from any particular dev framework. There are other books that are focusing on dev-level details. We are instead of focusing on protocols, and client-side and server-side design problems solutions.
Not sure if it has been seen but I mentioned in another comment that it would be helpful to have your thoughts and insights on:
a) RESTful services and the CAP theorem (side effects etc.).
b) ‘Good’ RESTful designs for the use of webhooks and the delegated authorization that arises in such contexts, e.g. oauth.
Excellent set of topics and great that you’ll be putting it out on O’Reilly’s Rough Cuts.
I know this isn’t a popular topic, but shouldn’t the use of REST over protocols beside HTTP be mentioned, maybe as a addendum or appendix?
This is one of the topics excluded particularly due to the lack of a sufficient experience that can be distilled into recipes applicable to a broad audience.
In Basic Authentication (Page 218), it is mentioned that “if the client knows a prior that server requires basic auth for a resource, it can include the authorization header with each request to avoid 401 error”. Can the same approach taken with Digest Authentication? – at least if we are ok to dis-regard nonce and qop? What are pros and cons in this approach?
In the case of digest auth, how can the client unilaterally decide to ignore the nonce?
Hello subbu,
I wish to know more details on JAX-RS Clients?
Our requirement is a device,which would be embedded in gasstation. It needs to talk to the JAX-RS webservice. Here the programming language of the client is C.
For JAX-RS questions, check out Bill Burke’s “RESTful Java with Jax-RS” (http://www.amazon.com/RESTful-Java-Jax-RS-Animal-Guide/dp/0596158041)