Right, but this does still does not cover specifying how the user agent should respond to a HTTP 200 and how that response integrates with a given application.
On 3/30/11 9:10 AM, "Dominik Tomaszuk" <[email protected]> wrote: >It could be supported in the same way as POST: 200 OK (describing or >containing the result of the action). HTTP in PUT and DELETE allowed 200 >if an existing resource is modified in PUT or if it is a successful >response (and it is consistent with the approach RESTful).
