From user-return-6809-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Sat Oct 10 00:28:53 2009
Return-Path: <user-return-6809-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org>
Delivered-To: apmail-couchdb-user-archive@www.apache.org
Received: (qmail 11689 invoked from network); 10 Oct 2009 00:28:53 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 10 Oct 2009 00:28:53 -0000
Received: (qmail 46918 invoked by uid 500); 10 Oct 2009 00:28:51 -0000
Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org
Received: (qmail 46837 invoked by uid 500); 10 Oct 2009 00:28:51 -0000
Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@couchdb.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@couchdb.apache.org>
List-Post: <mailto:user@couchdb.apache.org>
List-Id: <user.couchdb.apache.org>
Reply-To: user@couchdb.apache.org
Delivered-To: mailing list user@couchdb.apache.org
Received: (qmail 46827 invoked by uid 99); 10 Oct 2009 00:28:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Oct 2009 00:28:51 +0000
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=FS_REPLICA,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of aventurella@gmail.com designates 209.85.211.183 as permitted sender)
Received: from [209.85.211.183] (HELO mail-yw0-f183.google.com) (209.85.211.183)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Oct 2009 00:28:42 +0000
Received: by ywh13 with SMTP id 13so1675210ywh.29
        for <user@couchdb.apache.org>; Fri, 09 Oct 2009 17:28:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:date:message-id:subject
         :from:to:content-type;
        bh=sDySRzVz64MFsVIQTKbA9PawxBWbywtYJzq1bygJdis=;
        b=aFQbyTA5++m5rJE7cdUynw5+dp0XKCCrBTigXrFzZohq+6cD69nmtHi0QCX1k3Qrjf
         kaNdOy3kPkKElt0hrLLGLREsPSJHfIbv6DX0OZ8EZRRyiUues5PfMer/nq1VgmNeAtwg
         JM/I4L8u+WnfRHaJt0LvrtILiNTXB07+tdfGk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=ErJJpNanoJmLUXMzACkT3MdWBtTZx606y2qbe1gO08WOzSK7qcQhbTi7wEVl9f/z/E
         Hrs0/X9QARevmPs60btR7iBr8RBtYVLJ9TzHScUTsge71uYvssrikMDImdRS3lqTCaia
         f7VwwFCL3ISoQsCdQZmC/G1uX5qXdUwUCRES4=
MIME-Version: 1.0
Received: by 10.90.20.3 with SMTP id 3mr1771797agt.83.1255134501383; Fri, 09 
	Oct 2009 17:28:21 -0700 (PDT)
Date: Fri, 9 Oct 2009 17:28:21 -0700
Message-ID: <ec6557c00910091728r2a53cd14pbba1a035fc83c649@mail.gmail.com>
Subject: Authorize Replication?
From: Adam Venturella <aventurella@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

If I have 2 DBs: "A", and "B" on my server, and I want to replicate
(have the local pull from the master) "A" to another server, I get how
that works.  But what if only certain people are allowed to replicate
"A", how would I arrange that?  For example, I do not want the same
user to be able to replicate "B", only "A".  To add one more layer on
this, at some point, I want to be able to grant the user the ability
to replicate "B" as well as "A".

Is there a replication permission that can be set in the ACL or
another means to achieve this?