To be RESTful or not to be
James Thurber once voiced that:
It is better to know some of the questions than all of the answers.
Indeed, as anyone who has ever pondered REST and the hip implications of implementing RESTful applications knows, the question that often pops up is:
Is this URI RESTful?
Of course, since REST is neither a standard nor some product you can buy, but simply a style of designing applications the question has many answers, depending on who decides to answer it.
In the course of trying to answer this same question for various people, someone pointed me to an interesting resource dubbed “Common REST Mistakes“, authored by Paul Prescod (who co-authored the XML Handbook). Paul’s mistakes page is an easy read and quite helpful, especially if you are asking yourself whether or not something is truly RESTful. In essence, this page attempts to answer the RESTful or not question by stating what’s not RESTful.
Keep in mind, REST is a style and thus there are strict implementations and loose implementations, man.
| Related odds and ends | ||
|---|---|---|
1 comment Wednesday 10 Sep 2008 | Software Development
One Response to “To be RESTful or not to be”
[...] one. What’s more, specific parameters are passed in as a String type. Note, this is URL is as unRESTful as it can [...]