On Mar 7, 2009, at 11:35 PM, Antony Blakey wrote:
On 08/03/2009, at 1:39 PM, Chris Anderson wrote:
On Sat, Mar 7, 2009 at 6:01 PM, Antony Blakey <[email protected]
> wrote:
I don't see how this would solve the problem of e.g. double
invocations of a
replicate/compact/purge POST. I'm not sure what kind of delays
between
double POSTs one needs to deal with, but given that POSTs (and
maybe all
methods) do have this problem (regardless of whether the error is
in the
browser stack or middleware), this would seem to be a generic
solution that
cannot be solved in the client.
The ingredients for solving it are deterministic revs and
non-colliding client-specified docids.
I must be missing something - how does this stop a double POST to /
replicate et al caused by a browser stack or middleware error?
Replication and compaction are idempotent.
Non-sequitur, you working on getting that file name patch finished? It
would be nice to have that for 0.9.0
-Damien
