Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of johnlicheng@gmail.com
 designates 209.85.218.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABvT1DH7hkDj50GPDSE8Y49Lt8f8-APeLh0UpTv=tYwQp651CQ@mail.gmail.com>
References: 
 <CAJzZBAQuNCQ58oAHe2vLbxx_w1zfGHjiCx95b+euDTm+d2A-uA@mail.gmail.com>
 <E0B25DB2-AF24-4E05-80B2-301AFFC974BC@couchbase.com>
 <CABvT1DH7hkDj50GPDSE8Y49Lt8f8-APeLh0UpTv=tYwQp651CQ@mail.gmail.com>
From: John Cheng <johnlicheng@gmail.com>
Date: Thu, 18 Aug 2011 15:08:55 -0700
Message-ID: 
 <CAJzZBAT-83EYWwjSOjqPGLkXLZebRgQoZfD=+oBp1JsiRRR-ow@mail.gmail.com>
Subject: Re: The if-match header
To: user@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Thanks! I've been doing a bit of testing with "Expect: 100-continue"
and passing revision id in the header. I was expecting that this would
allow CouchDB to detect conflicts without the client having to send
data. But I'm not seeing much of a difference. Does CouchDB wait for
the client to send the whole document before responding whether there
was a conflict or not?


On Thu, Aug 18, 2011 at 2:06 PM, Robert Newson <rnewson@apache.org> wrote:
> That's core CouchDB.
>
> On 18 August 2011 21:46, Jens Alfke <jens@couchbase.com> wrote:
>>
>> On Aug 18, 2011, at 1:41 PM, John Cheng wrote:
>>
>> Does anyone know if this is unique to couchbase?
>>
>> The If-Match: / If-None-Match: / ETag: headers, and the algorithm for re=
jecting conflicting updates by comparing eTags, are fundamental parts of HT=
TP 1.1. And they=92re used by a lot of REST APIs, like the Atom Publishing =
Protocol, and by WebDAV.
>>
>> =97Jens
>>
>


--=20
---
John L Cheng