Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of wickedgrey@gmail.com
 designates 209.85.212.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <529E20E8.2070900@bigbluehat.com>
References: <529DE44C.4090400@bigbluehat.com>
	<529DFA3E.3010706@gmail.com>
	<CAHdjipJ0J_8zj2z3y1DbfbGHHVhx4LVGGF2AGkQkC+t5NGPQPw@mail.gmail.com>
	<529E20E8.2070900@bigbluehat.com>
Date: Thu, 5 Dec 2013 09:46:34 -0800
Message-ID: 
 <CADa34LCbdCDsZ7ajUheYRBWUXiWwnNf9bWLve03aA9GSjmx8oQ@mail.gmail.com>
Subject: Re: [PROPOSAL] new underscore namespacing
From: "Eli Stevens (Gmail)" <wickedgrey@gmail.com>
To: CouchDB Developers <dev@couchdb.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Dec 3, 2013 at 10:20 AM, Benjamin Young <byoung@bigbluehat.com> wrote:
> Sphinx (for one...among many...), uses "_*" prefixed folders for it's
> styles, templates, etc. So does Github's ghpages.
...
> The point with "/_/" was to narrow the surface area of the API.

I'd like to point out that if the goal is to reduce API surface area
to reduce collisions, using "_couchdb" for metadata is much less
likely to collide than "_".  It's also much more user friendly once
the data is outside of CouchDB proper ("where is this doc._.id coming
from?" etc.).

Cheers,
Eli