PUT is used by FB to update the comment because an existing resource is being updated, and that is what PUT does (updates a resource). PUT happens to be idempotent, in contrast to POST.
The difference between POST and PUT is that PUT is idempotent, that means, calling the same PUT request multiple times will always produce the same result (that is no side effect), while on the other hand, calling a POST request repeatedly may have (additional) side effects of creating the same resource multiple times.
I'm building a RESTful API using Zend Framework via the Zend_Rest_Route. For uploading of files, should I use PUT or POST to handle the process? I'm trying to be as consistent as possible with the
Gili, below you now also want to throw out PUT. I think you need to re-write the question from scratch. The web seems to get by with GET and POST so perhaps those are sufficient.
The difference between the PUT and PATCH requests is reflected in the way the server processes the enclosed entity to modify the resource identified by the Request-URI.
PUT and PATCH methods are similar in nature, but there is a key difference. PUT - in PUT request, the enclosed entity would be considered as the modified version of a resource which residing on server and it would be replaced by this modified entity.
I keep a key-value storage in the server for the client. If the user sends key "k1", then I upsert it to the database. Is this considered POST or PUT? Also I have another operation that removes all
