Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 67137 invoked from network); 6 Apr 2011 21:47:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Apr 2011 21:47:54 -0000 Received: (qmail 7394 invoked by uid 500); 6 Apr 2011 21:47:52 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 7358 invoked by uid 500); 6 Apr 2011 21:47:52 -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 7345 invoked by uid 99); 6 Apr 2011 21:47:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 21:47:52 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=FREEMAIL_FROM,FS_REPLICA,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of email.workbench@gmail.com designates 209.85.161.52 as permitted sender) Received: from [209.85.161.52] (HELO mail-fx0-f52.google.com) (209.85.161.52) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2011 21:47:44 +0000 Received: by fxm6 with SMTP id 6so2254815fxm.11 for ; Wed, 06 Apr 2011 14:47:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EVYLe2ndIi5APS6/2sWVmP2iLAzlaJTWxnz5p4JqEyQ=; b=YJ6y45+i0qgR0JcYKxc2FK5Nd/8a6jKzyGQGcqOcmSAk2rEuCxROz46Dps8+Q+cbVE ldd8bmiycrGseLLEKEe/w/WqA1aTz7NuD27GzsbElTpnp3O8erbgxCuNFTyJ2jf8WCRy k1qZVDAA2tcQ5JN5du2qSX/4XuMYSDLWyI+Zw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=UtMJ8WIAkgQm044Xn/AiC7/ZR1E/5ihsEjLWox7FIQiE+fXjnm9ER/pzEjLpb3Mimh RIHPas6Zpicss960kHOJy5syiPy0zkwjze2cXmOnjKcYU6GuIslFqKR79F520xCjaM6m N6m10GEgbtzXinEszyxHp62xxVSkeUA2Z2xdM= MIME-Version: 1.0 Received: by 10.223.27.7 with SMTP id g7mr117487fac.62.1302126444451; Wed, 06 Apr 2011 14:47:24 -0700 (PDT) Sender: email.workbench@gmail.com Received: by 10.223.121.82 with HTTP; Wed, 6 Apr 2011 14:47:24 -0700 (PDT) In-Reply-To: <4D9CD977.8080707@facilityone.com> References: <4D9CBEEB.3090102@facilityone.com> <4D9CD977.8080707@facilityone.com> Date: Wed, 6 Apr 2011 17:47:24 -0400 X-Google-Sender-Auth: -0wdsKTRSQ5iOeN65fWjZJ8pkTk Message-ID: Subject: Re: Peer-to-Peer Replication From: Zdravko Gligic To: Owen Marshall Cc: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org > What exactly are you wanting to accomplish here? In it's simplest form, consider a large community of members or peers, in which each member subscribes to one or more of a dozen CouchDB databases. Within each database, community members could post documents, comment and/or take other actions on any one doc. However, each of these actions would not be an update to the original docs but would rather be creations of new docs. The end result should be a situation in which each subscriber eventually ends up with all of the documents in their corresponding local CouchDB copy. > Whichever document has the largest _rev count is the most recent. For simplicity, lets take this part out of the discussion by assuming that any one document would be modifiable and/or deletable only by its original author/poster.