REST Resources

From time to time people ask me questions about RESTful architecture. I thought it might be helpful to list the resources that I keep near at hand for asnwering tricky REST questions.


  • RFC2616 Hypertext Transfer Protocol: If you haven’t read this RFC, you might be surprised at what you don’t know about HTTP. I keep a printed copy nearby at all times.
  • RFC5988: Web Linking. You might not have heard of this one, but I think it’s one of the more important recent developments in HTTP from a RESTful standpoint. REST is all about hyperlinks, but how do you link a non-HTML resource – like an image, for instance – to other resources? This RFC tells you how.
  • URI Templates. This one’s still a draft. In general forcing clients to build their own URIs is bad form; contrary to a zillion “How to use our RESTful API” articles you may have read, URIs are supposed to be opaque. However, sometimes URI construction is inevitable; when that’s the case, we can at least specify it in a machine-understandable format with URI templates.



What about you? What are your favorite resources on RESTful architecture?

Note: Any comments to the tune of “blah blah REST orthodoxy blah blah zealots blah blah real world blah blah who cares” will be summarily deleted. The books and articles listed above are by real developers who have solved real deficiencies in HTTP APIs using RESTful principles. If you and/or your users don’t have the problems these techniques address, that’s fine. This article isn’t for you. Move along.

Enhanced by Zemanta