Forget about the Wikipedia article, you should first read this: http://tomayko.com/writings/rest-to-my-wife http://tomayko.com/writings/rest-to-my-wife. Other e

Forget about the Wikipedia article, you should first read this: http://tomayko.com/writings/rest-to-my-wife http://tomayko.com/writings/rest-to-my-wife. Other explanations I found good are: http://www.reddit.com/r/programming/comments/91ups/ask_proggit_can_anyone_explain_to_me_in_a/ http://www.reddit.com/r/programming/comments/91ups/ask_progg... and http://jcalcote.wordpress.com/2009/08/06/restful-transactions/ http://jcalcote.wordpress.com/2009/08/06/restful-transaction... Unfortunately, REST and RESTful have become buzzwords, roughly take to mean "good" way of doing things. Selecting an approach just because it is the buzz de jour is dangerous. I've had managers ask me about an API, "But is it RESTful?" without an iota of understanding why they need it.