incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Kocoloski <adam.kocolo...@gmail.com>
Subject Re: handling simultaneous identical replications
Date Thu, 05 Mar 2009 17:46:27 GMT
On Mar 5, 2009, at 8:06 AM, Jan Lehnardt wrote:

>
> On 5 Mar 2009, at 14:00, Adam Kocoloski wrote:
>
>> On Mar 5, 2009, at 7:24 AM, Jan Lehnardt wrote:
>>> I understand this and Adam's option 3 to be the same. What am I  
>>> missing? :)
>>
>> No, not quite.  In Option 3 the two requesters get different  
>> responses.  A gets the result of the original request, B gets the  
>> result of the replication triggered automatically after the first  
>> one that replicates any updates to the DB which happened during the  
>> first pass.  If no updates occurred, B will receive the result of  
>> the first replication.
>>
>> Paul's Option 4 is more like Options 1 and 2, where A and B get  
>> identical responses.  The difference between 1 and 2 is just  
>> whether new updates get included in that response.
>
> Thanks for clearing that up. I prefer option 3.
>
> Cheers
> Jan
> --


Sounds like we're getting a consensus around Option 3, so I added that  
behavior to my GitHub branch.

Mime
View raw message