PUT or POST: The REST of the Story « Open Sourcery
http://jcalcote.wordpress.com/2008/10/16/put-or-post-the-rest-of-the-story
PUT vs POST in RESTful Web Service « vincenthome’s Tech Clips
http://vincenthomedev.wordpress.com/2008/12/18/put-vs-post-in-restful-web-service
"This explains when to use POST or PUT for creating new resources. The answer ultimately lies in who is responsible for determining the new resource’s URI. If the client is in charge, the client can use PUT to the new URI (like we did for user accounts) and the service can return a response code of 201 (“Created”). However, if the service is in charge of generating the new URI, the client should POST the new resource to a factory URI like we’ve done for bookmarks. Then, the service can return a response code of 201 (“Created”) along with the URI of the new resource in the response “Location” header."
Why PUT and DELETE?
http://www.artima.com/lejava/articles/why_put_and_delete.html
"In this interview, Elliotte Rusty Harold discusses the true meaning of PUT and DELETE."
Re: Meaning of PUT, with (gasp) evidence
http://www.imc.org/atom-protocol/mail-archive/msg05425.html
"FWIW, PUT does not mean store."