W3 also goes on to say that it's ok if a change occurs, as long as the user cannot request them and isn't held responsible:
"The important distinction here is that the user did not request the side-effects, so therefore cannot be held accountable for them." It's equivalent of saying "show me the state of document #3", and then making the same request an hour later, if you ask me. On Sat, 2009-01-03 at 13:45 +0000, Jason Davies wrote: > On 3 Jan 2009, at 13:41, Noah Slater wrote: > > On Sat, Jan 03, 2009 at 11:58:59PM +1030, Antony Blakey wrote: > >> GET is meant to be idempotent - > >> http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html. > > > > So? How does the idempotency of GET affect the UUID service? > > Quoting from the RFC: A sequence that never has side effects is > idempotent, by definition (provided that no concurrent operations are > being executed on the same set of resources). > > Hence the UUID service is idempotent, as it has no side effects. > > Jason > -- > Jason Davies > > www.jasondavies.com >
