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. -- Chris Anderson http://jchris.mfdz.com
