Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 95740 invoked from network); 14 Jun 2009 20:34:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Jun 2009 20:34:36 -0000 Received: (qmail 80834 invoked by uid 500); 14 Jun 2009 20:34:47 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 80743 invoked by uid 500); 14 Jun 2009 20:34:46 -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 80733 invoked by uid 99); 14 Jun 2009 20:34:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jun 2009 20:34:46 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com designates 209.85.132.244 as permitted sender) Received: from [209.85.132.244] (HELO an-out-0708.google.com) (209.85.132.244) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jun 2009 20:34:36 +0000 Received: by an-out-0708.google.com with SMTP id b6so2981577ana.5 for ; Sun, 14 Jun 2009 13:34:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=dUKM4GQgYhSkgJm+Bj4pT1k/HGwXjPowx6FInraflGg=; b=j0S5TbDaPbT7aYSbEOGQRuvAbkYycuh6+EDzgRoWF7vsrF89MMkwMS0Fe++rDBB7po 1UbvCTWKvAPRj+2NAgW86vfYJXiFcBFoCwKdN8NNIgr/BSl+4yeLxpuqg3n5v2WOIbnI aw68gKekQj2IGCb9/BL+rMo95fHXCtfXCvVLo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=UdnejBDs2fvJ3F2BCPA6ttzU2bMufHwWyfUChyoB91AP89WkSFlhTyj0Ti9PkYTCOi sgFCvVsHT5TTcMXzPtHtEJWsK4W50X7U847ZiXW8EDqWUxsY1ez5qYhdzhyj2YE06A6u 7+5iG4lzFeSrTNESY/YWm+X9fS8psXOlEvuvs= MIME-Version: 1.0 Received: by 10.100.110.19 with SMTP id i19mr7745377anc.1.1245011655579; Sun, 14 Jun 2009 13:34:15 -0700 (PDT) In-Reply-To: <0EFAA99E-2FF3-4FC3-B1AD-9FAF0B47653D@apache.org> References: <5c02bc4e0906141139t72597b87n1cf3eaf78a2e2838@mail.gmail.com> <0EFAA99E-2FF3-4FC3-B1AD-9FAF0B47653D@apache.org> Date: Sun, 14 Jun 2009 16:34:15 -0400 Message-ID: Subject: Re: ETA on Read Access Restriction From: Paul Davis To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Idle thought, but perhaps making views based on roles might be the way to g= o. Paul On Sun, Jun 14, 2009 at 4:11 PM, Damien Katz wrote: > Per-document reader access likely won't be 1.0 feature. It's not hard to = add > the restriction to the database, but it's much harder to add it to the vi= ew > engine to filter out docs from maps and reductions that the user cannot > read. > > -Damien > > On Jun 14, 2009, at 2:39 PM, Avi Flax wrote: > >> Hi All, >> I'm thinking of building an app using CouchDB, but I need to be able to >> restrict certain users from retrieving certain docs and views. As far as= I >> can tell from searching the web, the mailing list, and the wiki, that >> feature's not yet built. >> >> I know I could achieve the desired features by building a server-side >> "proxy" app which would validate requests before passing them to Couch, >> but one of the things that attracts me to CouchDB is the possibility of >> building 2-tier apps instead of 3 tiers; i.e. just DOM/Javascript and >> Couch. >> >> So I'm just wondering: does anyone have a sense of when this functionali= ty >> might be landing in trunk? >> >> Thanks! >> Avi >> >> -- >> Avi Flax =BB Partner =BB Arc90 =BB http://arc90.com > >