Mark, The key challenge with this is that the server is given free reign over the posted entries metadata content. It can change anything and everything about the entry once it has been posted, including it's atom:id. If an Atom entry is not returned in response to the POST, the client would have to first perform a GET on the Location URI to get the atom:id before they could match what they POST'ed to what shows up in the Collections Atom feed, which works, but is inefficient. Making the response mandatory eliminates this problem.
- James Joe Gregorio wrote: > On 4/25/06, Mark Baker <[EMAIL PROTECTED]> wrote: >>> 8.1 Creating resources with POST >> [...] >>> If the server includes a body in the response, the >>> entity MUST be an Atom Entry Document representing the newly-created >>> resource, equivalent to that which would appear in the collection's feed >>> document. >> Why the MUST for the format? If the response body is optional (a good >> thing), then the client will already know how to handle the case when >> it doesn't get an Atom Entry back. > > The response body is no longer optional: > > http://www.imc.org/atom-protocol/mail-archive/msg04845.html > > -joe > > -- > Joe Gregorio http://bitworking.org >
