On 7/8/06, James M Snell <[EMAIL PROTECTED]> wrote:
http://www.intertwingly.net/wiki/pie/PaceNoChangeId #pragma section-numbers off == Abstract == For Draft-09 Clients should not be allowed to change the atom:id of entries. == Status == Proposed == Rationale == Clients should not be allowed to change the atom:id of entries == Proposal == {{{ 8.# Persistence of atom:id values When updating a collection member's atom:entry using PUT, clients MUST NOT change the value of the entries atom:id element.
I'm +1 on everything up to here.
Servers MUST reject attempts to modify the atom:id of a member entry with an appropriate 4xx HTTP response status code (e.g., 400 "Bad Request", 403 "Forbidden" or 409 "Conflict"). }}}
The server can do what it wants, which in my case my implementation overwrites the atom:id every time a client does a PUT. I know what the atom:id should be by the URI that the entry was PUT to, so why bother generating an error? -joe -- Joe Gregorio http://bitworking.org
