Absolutely +1 on not allowing the client to change the atom:id. Tim Bray wrote: >[snip] > But, since we're quoting RFC2616 chapter and verse, I note the > following: "If the Request-URI refers to an already existing resource, > the enclosed entity SHOULD be considered as a modified version of the > one residing on the origin server. " I take that to imply that sending > a PUT to the edit URI of an Atom Entry MUST NOT change the atom:id. > > -Tim > >
- Re: Meaning of PUT Kyle Marvin
- Re: Meaning of PUT Bill de hÓra
- Re: Meaning of PUT James M Snell
- Re: Meaning of PUT Joe Gregorio
- Re: Meaning of PUT Kyle Marvin
- Re: Meaning of PUT James M Snell
- Re: Meaning of PUT Kyle Marvin
- Re: Meaning of PUT James M Snell
- Re: Meaning of PUT Tim Bray
- Re: Meaning of PUT James M Snell
- Re: Meaning of PUT, with (gasp) evidence James M Snell
- Re: Meaning of PUT, with (gasp) evidence Thomas Broyer
- Re: Meaning of PUT, with (gasp) evidence Bill de hÓra
- Re: Meaning of PUT, with (gasp) evidence Tim Bray
- Re: Meaning of PUT, with (gasp) evidence Robert Sayre
- Re: Meaning of PUT, with (gasp) evidence Kyle Marvin
- Re: Meaning of PUT, with (gasp) evidence John Panzer
- Re: Meaning of PUT, with (gasp) evidence Mark Baker
- Re: Meaning of PUT, with (gasp) evidence Kyle Marvin
- Re: Meaning of PUT, with (gasp) evidence Jan Algermissen
- Re: Meaning of PUT, with (gasp) evidence Thomas Broyer
