3 ms·
couchdb then technically violates this due to revision numbers
by keefe 16y ago
couchdb then technically violates this due to revision numbers
- epochwolf 16y agoI'd say the mapping is good enough. PUT updates a current object, which can be done again. POST creates a new object which can't be repeated without producing another article. CouchDB has automatic versioning which is mostly transparent to most operations. (on a single instance)
- keefe 16y agoIt was a nitpicky comment, I guess cause I am contemplating the meaning of idempotent. Two identical PUTs on an existing doc will not change the database so I guess that's OK, but their response will be different insofar as the 2nd will fail.
- epochwolf 16y agoI don't think the failed response matters. You can replay a PUT request without altering the state on the server. (Aside from the single object you're manipulating.) Replaying a POST gets you two objects with the same data.
- keefe 16y agoI think you're right because the 2nd PUT doesn't change the value of variables on the server.