Content-Location and etag, was: I-D Action:draft-dusseault-http-patch-16.txt

Hi,

in response to earlier comments the draft now has the following example 
in <http://tools.ietf.org/html/draft-dusseault-http-patch-16#section-2.1>:

--- old ---
    This example illustrates use of a hypothetical patch document on an
    existing resource.  The 204 response code is used because the
    response does not have a body (a response with the 200 code would
    have a body) but other success codes can be used if appropriate.

    Successful PATCH response to existing text file

    HTTP/1.1 204 No Content
    Content-Location: /file.txt
    ETag: "e0023aa4f"
--- old ---

It's good that Content-Location was added, making this consistent with 
the proposed resolution of 
<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/110>.

However, it would be even better it there was a short explanation, such 
as in:

--- new ---
    This example illustrates use of a hypothetical patch document on an
    existing resource.

    Successful PATCH response to existing text file:

    HTTP/1.1 204 No Content
    Content-Location: /file.txt
    ETag: "e0023aa4f"

    The 204 response code is used because the response does not
    carry a message body (which a response with the 200 code would have).
    Note that other success codes could be used as well.

    Futhermore, the ETag response header field contains the ETag for
    the entity created by applying the PATCH, available at
    http://www.example.com/file.txt, as indicated by the Content-Location
    response header field.
--- new ---

This moves part of the explanation below the response, expands on the 
Content-Location thingy and replaces "body" by "message body" (also adds 
a ":" after the subtitle).

Best regards, Julian

Received on Thursday, 26 November 2009 12:59:00 UTC