Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 19775 invoked from network); 18 Aug 2010 16:29:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Aug 2010 16:29:57 -0000 Received: (qmail 38944 invoked by uid 500); 18 Aug 2010 16:29:57 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 38892 invoked by uid 500); 18 Aug 2010 16:29:56 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 38884 invoked by uid 99); 18 Aug 2010 16:29:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Aug 2010 16:29:56 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fdmanana@gmail.com designates 209.85.213.52 as permitted sender) Received: from [209.85.213.52] (HELO mail-yw0-f52.google.com) (209.85.213.52) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Aug 2010 16:29:50 +0000 Received: by ywl5 with SMTP id 5so426598ywl.11 for ; Wed, 18 Aug 2010 09:29:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=b7ngETjgpiaiK9ashyCOXs3cT+utBI8rjQZSbJTjrMI=; b=gz9N/w1kfhP2JnOL40cYyTe0Dh43nBn6GbuXx8X2KJungr785C4F4dZW5ichUzHnqS IYvPYy9kq81fOpLQ0QC93lmdbP6CnwZdZzxkZuNLoZQQe/1b2XTv4eiDMINvXwowzXAL ApPpQ8c3uB/cFr6u+VCEuPSAexobhL4j4oG+k= 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:content-type; b=j1k5iWXHUh6BsyJizYewvIo1diB2aVLj6m5GYZtxCnFnO+YCBhHCOTTTF6vWHUSSVl Ck7D2OPUi9A3YvM5M57JCPcJGjxUDCJl4i97wB8DnSKXJxBTL4p06DTCm2nMU+seOYir 8dvLmyGNPtbsOEb+6oHNmoWMg9iYck+rTcMhY= MIME-Version: 1.0 Received: by 10.151.46.14 with SMTP id y14mr536511ybj.242.1282148967770; Wed, 18 Aug 2010 09:29:27 -0700 (PDT) Sender: fdmanana@gmail.com Received: by 10.231.68.70 with HTTP; Wed, 18 Aug 2010 09:29:27 -0700 (PDT) In-Reply-To: References: Date: Wed, 18 Aug 2010 17:29:27 +0100 X-Google-Sender-Auth: 7LkEO6mOzOK5Ds4HDyl_gUgQAz4 Message-ID: Subject: Re: request.sec or request.secObj ? From: Filipe David Manana To: dev@couchdb.apache.org Content-Type: multipart/alternative; boundary=0015174c36b2c5f64e048e1b91d7 --0015174c36b2c5f64e048e1b91d7 Content-Type: text/plain; charset=UTF-8 secObj as well On Wed, Aug 18, 2010 at 5:26 PM, Benoit Chesneau wrote: > Hi all, > > I want to expose the security object to shows, lists, updates and > validate function, so we could eventually add some metadata to a db > (idea come from jcrhis@) . It's relatively easy but I hesitate about > the variable name . My preferece go for secObj (like we have userCtx). > What do you think ? > > - benoit > -- Filipe David Manana, fdmanana@gmail.com, fdmanana@apache.org "Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men." --0015174c36b2c5f64e048e1b91d7--