2006/6/2, Joe Gregorio <[EMAIL PROTECTED]>:
> I'd like to point out that the only way to correlate a POSTed member
> with whatever the server creates is via the immediate response.
This is why I wanted the return of an Atom Entry on POST to be
a MUST and not a SHOULD.
You have the value of the Location response header, which you can
dereference to retrieve the Atom Entry Document representation of th
newly-create resource.
Sending that Atom Entry (or a modified form) as the response body
(along with an appropriate Content-Location header) is just an
optimization trick so that clients won't need to perform a GET just
after the response to the POST, nothing more, nothing less.
I'd be +1 to mandating the Location response-header field in 201
(Created) responses, though (as I read the RFC2616, it seems to me
that it's "only" a SHOULD there)
--
Thomas Broyer
