Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 89019 invoked from network); 1 Mar 2011 21:39:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Mar 2011 21:39:14 -0000 Received: (qmail 60634 invoked by uid 500); 1 Mar 2011 21:39:13 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 60593 invoked by uid 500); 1 Mar 2011 21:39:12 -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 60585 invoked by uid 99); 1 Mar 2011 21:39:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Mar 2011 21:39:12 +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 (athena.apache.org: domain of jchris@gmail.com designates 209.85.210.180 as permitted sender) Received: from [209.85.210.180] (HELO mail-iy0-f180.google.com) (209.85.210.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Mar 2011 21:39:08 +0000 Received: by iyf40 with SMTP id 40so5436970iyf.11 for ; Tue, 01 Mar 2011 13:37:58 -0800 (PST) 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 :content-transfer-encoding; bh=qMgJBdg13RV5Q9qyqsLhTEDy4ZOe4uI/OhQSj2foA9k=; b=b6RNURfbI6WFrS4Aa/MHuZNNgHlslYAlMlwxJfBVLoCqM0YZnyZF3SAeAS+v/bqrK9 m19wNHZ+jZTTP0vXRNX5OIdh6qOjuKp15HvdpG6JBn2n8mZ65OjmhMHIpxllv4uSnwVv NX1tOgN+06ibL41OYDvgfSjpZEolqaER102Qk= 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 :content-transfer-encoding; b=sRq2mV5T03oxNWUlzob/E9ryU5QEMEKwTSaNb1slLCZ51drsGMND8NfxByxBTBdk0y JxOjoGysDBw3joK1Q15xOb5+bP5ODrFTpGiAu8U/9wWLTvbRWeRyrSlFmnbo8g7y+ES1 GGEd4GZ8RzwvtnQsafIkvkocfPz3YenY9lYRQ= MIME-Version: 1.0 Received: by 10.42.229.9 with SMTP id jg9mr2866016icb.146.1299015478329; Tue, 01 Mar 2011 13:37:58 -0800 (PST) Sender: jchris@gmail.com Received: by 10.42.239.196 with HTTP; Tue, 1 Mar 2011 13:37:58 -0800 (PST) In-Reply-To: References: Date: Tue, 1 Mar 2011 13:37:58 -0800 X-Google-Sender-Auth: TXiRp_e5vHD45AJxK6hbR77oKlA Message-ID: Subject: Re: Write-only for users? From: Chris Anderson To: user@couchdb.apache.org Cc: Jonathan Geddes Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Feb 14, 2011 at 8:25 AM, Jonathan Geddes wrote: > These all sound like good ideas that will work, but they seem like a > lot of work for a fairly simple task. > > Anyone know the rational behind couch not supporting write-only for > users? Open databases are cool, but sometimes you need closed ones to > protect privacy. I would like a write-only "dropbox" style database. I've wanted this for a while, but sadly sits at the bottom of my todo list. Chris > > Thanks all for the responses. > > --Jonathan > > On Mon, Feb 14, 2011 at 12:04 AM, Aravinda VK > wrote: >> Sorry I missed a note, the example blog(http://hosabelaku.aravindavk.in)= has >> some issue with Internet explorer. (Didn't get the Windows machine to te= st >> it and fix :) ) >> >> On Mon, Feb 14, 2011 at 12:30 PM, Aravinda VK wrote: >> >>> I had the similar situation while creating my photoblog. When user add >>> comments to a blog then other users can see the sensitive informations = like >>> email. >>> >>> So my approach, >>> Created the comments app as an independent system(Like Disqus) >>> Added PHP layer to it and given read and write permission to Admin for >>> comments database. >>> The PHP layer acts as API server. >>> >>> When user adds comment, It will be submitted to PHP layer using JSONP(s= ince >>> cross domain). >>> To load the comments, I just pass URL of blog/page to get comments rela= ted >>> to that URL. (Email will be excluded by PHP layer while serving) >>> >>> My photoblog is created as couchapp, and gets comments from PHP layer u= sing >>> JSONP. >>> >>> Except for comment system, everything else is complete couchapp. >>> >>> Advantage here is, We can use the same comments system for multiple >>> websites. >>> >>> You can visit the blog which I am talking about >>> http://hosabelaku.aravindavk.in (This photoblog is in Kannada, Language= of >>> Karnataka, India http://en.wikipedia.org/wiki/Kannada) >>> >>> Source code is not shared yet. Need to cleanup the code bit. Will share >>> once it is ready :) >>> >>> -- >>> Regards >>> Aravinda | =E0=B2=85=E0=B2=B0=E0=B2=B5=E0=B2=BF=E0=B2=82=E0=B2=A6 >>> http://aravindavk.in >>> >>> On Mon, Feb 14, 2011 at 3:22 AM, Jonathan Geddes < >>> geddes.jonathan@gmail.com> wrote: >>> >>>> couchdb users, >>>> >>>> I'm thinking of using a couchapp for an upcoming project, but there is >>>> one capability that I'm unsure of. >>>> >>>> I need a database that anyone can post to, but only admin can read >>>> from. The requirement is to allow users to post personal information >>>> that other users cannot see. If I understand the couchdb permissions >>>> model correctly, for a given db, anyone who can create documents can >>>> also read documents. >>>> >>>> Is there a way to do this with a couchapp? It seems a shame to have to >>>> add "middleware" just to get this one capability. >>>> >>>> thanks, >>>> >>>> --Jonathan >>>> >>> >>> >>> >>> >>> >> >> >> -- >> Regards >> Aravinda | =E0=B2=85=E0=B2=B0=E0=B2=B5=E0=B2=BF=E0=B2=82=E0=B2=A6 >> http://aravindavk.in >> > --=20 Chris Anderson http://jchrisa.net http://couch.io