I'm noticing that I have to use the exact cas object returned from a "get" operation as the cas option in a subsequent "set" operation. If I make a copy of the cas object e.g. cas = JSON.parse(JSON.stringify(cas)) then the "set" call fails with keyAlreadyExists.
So the question is, how to I manage to implement cas update conflict prevention when the object retrieved by "get" required serialisation before it is modified, and subsequently "set"?
(In my case this is because the document modification occurs on a remote client communicating with the server over http REST interface, which surely must be a very common use case?)
No answers yet