On 8 Mar 2009, at 00:22, Antony Blakey wrote:
On 08/03/2009, at 4:41 AM, Chris Anderson wrote:
Currently it's recommended not to POST new documents without ids to
CouchDB. Due to HTTP protocol issues this can result in duplicate
document creation.
I've never really understood this. Wouldn't it mean that all POST
operations in CouchDB need to be made idempotent by the server
because they might be erroneously repeated by middleware?
Correct, a bug in Safari / CFNetwok brought this up.
Given that POSTing to a collection, resulting in a response with a
Location header is a fundamental part of the REST model, how do
other REST APIS deal with this problem?
http://lmgtfy.com/?q=rest+non+idempotent+POST+to+a+collection&l=1
and more here:
http://lmgtfy.com/?q=rest+non+idempotent+POST+to+a+collection
Cheers
Jan
--
