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 C9EFF8E7F for ; Thu, 1 Sep 2011 15:04:24 +0000 (UTC) Received: (qmail 99489 invoked by uid 500); 1 Sep 2011 15:04:23 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 99404 invoked by uid 500); 1 Sep 2011 15:04:22 -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 99396 invoked by uid 99); 1 Sep 2011 15:04:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 15:04:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=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 paul.joseph.davis@gmail.com designates 209.85.215.172 as permitted sender) Received: from [209.85.215.172] (HELO mail-ey0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 15:04:16 +0000 Received: by eye4 with SMTP id 4so2319556eye.17 for ; Thu, 01 Sep 2011 08:03:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=Zp3pZPit48iOsQcnH5tAp7JZUiSmmcDKk2cNW9bQZYw=; b=Tot6FIEqCNm4oyH/pWxurXE2LGr0la0UCZNWzju0XWp6+bPX2cNJeH3a0nxvRnCG+e 0PPTMcYEcL++TDY/usW64/WEgzF6QVKlsmdIRKi7dgsi/kmmNug8zl+NzJu1dbK1nRzv P94Nln9qZ1nX38B9Gw8ZZGPvxqzRe88QIWiwY= Received: by 10.52.94.176 with SMTP id dd16mr331113vdb.369.1314889436226; Thu, 01 Sep 2011 08:03:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.29.1 with HTTP; Thu, 1 Sep 2011 08:03:16 -0700 (PDT) In-Reply-To: <4E5F8FE3.6020709@couchone.com> References: <4E5EDB53.3050503@gmail.com> <3355CDD2-0463-4083-9B86-E103CB259AFD@ecstatic.com> <4E5F8FE3.6020709@couchone.com> From: Paul Davis Date: Thu, 1 Sep 2011 10:03:16 -0500 Message-ID: Subject: Re: Database synchronization protocol? To: user@couchdb.apache.org Cc: Mikeal Rogers Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org The only thing you need to make replication work are the algorithms around couch_key_tree. Then if you want to make it incremental, you need the update sequence index. After that its all just optimization. On Thu, Sep 1, 2011 at 9:00 AM, Benjamin Young wrot= e: > Oh dear... ;) Not at all the same thing. :) > > I agree with Stuart that it'd be great to see the CouchDB replication > "protocol" (HTTP + MVCC + _changes feed...mostly) codified into a > specification that could be implemented anywhere. There's working being d= one > to prove that it can be with Mikeal's PouchDB project: > https://github.com/mikeal/pouchdb > > Perhaps the first step looks like listing off the key pieces of the puzzl= e > and things that might be less obvious like needing consistent, though > arbitrary, conflict "resolution" (always selecting the same winner). > > Anyone know if there's a wiki page or blog post that would get this proce= ss > started? If not, anyone know enough about the feature to start one? :) > > Thanks, > Benjamin > > On 9/1/11 9:07 AM, Roger Rohrbach wrote: >> >> This isn't exactly what you're asking for, but behold: SyncML >> (http://www.openmobilealliance.org/tech/affiliates/syncml/syncmlindex.ht= ml). >> >> And weep. =A0:-( >> >> >> On Sep 1, 2011, at 3:09 AM, Stuart Rackham wrote: >> >>> In the same way that UnQL standardizes document database queries does >>> anyone know of any work being done on a standardized document database >>> synchronization protocol? > >