Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E2ABE6365 for ; Fri, 8 Jul 2011 04:28:21 +0000 (UTC) Received: (qmail 37413 invoked by uid 500); 8 Jul 2011 04:28:19 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 37048 invoked by uid 500); 8 Jul 2011 04:28:03 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 37030 invoked by uid 99); 8 Jul 2011 04:27:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jul 2011 04:27:57 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of orenshani7@gmail.com designates 209.85.161.44 as permitted sender) Received: from [209.85.161.44] (HELO mail-fx0-f44.google.com) (209.85.161.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jul 2011 04:27:49 +0000 Received: by fxe6 with SMTP id 6so1718540fxe.31 for ; Thu, 07 Jul 2011 21:27:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=XSS6tzTCidcmDgPe8QRjTI+CsxD7TT+3/cop4nX3hiw=; b=EFEoPt9PB+zu9Z1mE1NbfBeILmylpwo5DoLWMwqI1IQG0L4TyxahBusDGGGcO/yDSJ GheAWshkY2Gei2IbESbXnN2bqELe6dzA9nX76BIzJABJoZrG66W1+7J/oaaVgPGW1NXp 79d6nFe4nuakFJZu76XJczn9gP/CeT5IQ43II= Received: by 10.223.101.139 with SMTP id c11mr1285618fao.81.1310099249274; Thu, 07 Jul 2011 21:27:29 -0700 (PDT) Received: from [192.168.1.101] ([77.127.252.66]) by mx.google.com with ESMTPS id q14sm7120261faa.3.2011.07.07.21.27.27 (version=SSLv3 cipher=OTHER); Thu, 07 Jul 2011 21:27:28 -0700 (PDT) Message-ID: <4E16872E.6090201@gmail.com> Date: Fri, 08 Jul 2011 07:27:26 +0300 From: Oren Shani User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10 MIME-Version: 1.0 To: user@couchdb.apache.org CC: Mark Hahn Subject: Re: use case for conflict resolution? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi mark Have a look here: http://www.ruby-forum.com/topic/1750014#new Hope that helps... Oren On 07/08/2011 02:57 AM, Mark Hahn wrote: > I've never implemented code for resolving conflicts. I've always > retried updates that failed by re-reading and updating until it > succeeds, so the last updater always wins. My apps have always been > cases where updates by single users are the norm. > > I'm now facing a new app where multiple updates will be more common. I > know from the docs how to implement conflict resolution but I've never > seen an example or use case. Can someone point me to an example of > real-world usage? If not, does anyone have a story of their own use > case to tell?