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 686D695AE for ; Tue, 26 Jun 2012 22:28:42 +0000 (UTC) Received: (qmail 1427 invoked by uid 500); 26 Jun 2012 22:28:40 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 1373 invoked by uid 500); 26 Jun 2012 22:28:40 -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 1365 invoked by uid 99); 26 Jun 2012 22:28:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2012 22:28:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of wordituk@gmail.com designates 209.85.216.182 as permitted sender) Received: from [209.85.216.182] (HELO mail-qc0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2012 22:28:33 +0000 Received: by qcsg15 with SMTP id g15so257333qcs.27 for ; Tue, 26 Jun 2012 15:28:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GJr4sdXc+i7+yzV0WAaV5z1vyuXixoKq78FYOJplFYw=; b=qd0CoC8ceXfEHECMtsbv3qpKnmAOOaKJs7WnNRJNDjAJiQAaJHgCJqBUGyE2f22IV8 0NTzGLdBk3XRNHgOXU2a7KQ2kNMKyu33m/Ex8LL/PUQQ85DmQe7tkMVVKCTY8lwJXNtO 55QfhDoznUnzFOB01FY/oVrA3RbAAndUHrPU7PUYyQIuzvdrVvTVexgVsi1WvUEobTN1 gl2nrDpLugWcJMHMBLizJykw8VRw3DzDPMZdYPN3Yk3Aphqkmy2d788pC2TVFOgKWwln uyaAk+rmNNye5PJl6bYB7Ng3q3o1KBHDMOPPREbovJeYOstx94LzSTYQSUNB9jWD2xMW IzrA== MIME-Version: 1.0 Received: by 10.224.18.129 with SMTP id w1mr16117012qaa.56.1340749692104; Tue, 26 Jun 2012 15:28:12 -0700 (PDT) Received: by 10.229.187.143 with HTTP; Tue, 26 Jun 2012 15:28:12 -0700 (PDT) Received: by 10.229.187.143 with HTTP; Tue, 26 Jun 2012 15:28:12 -0700 (PDT) In-Reply-To: References: <72B4B717-86B6-4D06-AC60-8D1C081E127B@davisworld.org> Date: Wed, 27 Jun 2012 00:28:12 +0200 Message-ID: Subject: Re: Reader ACLs From: Wordit To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=bcaec5196183216f0f04c3679d6c --bcaec5196183216f0f04c3679d6c Content-Type: text/plain; charset=UTF-8 Thanks for the clarifications so far. Would this simple approach work? Bob has own db. He is admin and sets readers to "Anna, Fred". Bob creates document. Now only He, Anna and Fred can read the document, correct? Bob edits /_security doc, adding Sara to "readers", so she can read too. In other words, Each user owns a db with their docs, and can set the readers ACL. It is an app for writers to critique each other. Copyright plays a role, hence the stricter reading privileges. Would this work or am I missing something? Marcus --bcaec5196183216f0f04c3679d6c--