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 antony.blakey@gmail.com
 designates 209.85.142.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=VKCClPcvaSg+PSWcjOVRxmy9VS5igdxr2WWg3TrmHlMILnHCJ6NpT1qnGLK6qCTANM
         CJeXGcfAkPA6UidCH+28thTUmFfLx9PMsk7j55M3hjDBaZVy5hH8ys7WZ2gIIAnqr104
         uDRDXLNAv102G38UOkMleZMD+JPWznGV9Jlzk=
Message-Id: <81DEB393-6725-40F5-860C-FD9FB56D6B83@gmail.com>
From: Antony Blakey <antony.blakey@gmail.com>
To: dev@couchdb.apache.org
In-Reply-To: <FECFBB7F-E77D-412E-8E2D-9BACF163BCC9@gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: slash escaping (was 0.9.0 Release)
Date: Fri, 12 Dec 2008 07:33:39 +1030
References: <e282921e0812111139t499bfb08v56d8a0f4d29a8a39@mail.gmail.com>
 <0EC6A3E0-15BA-4BBB-A0A3-9ED9D04E3C40@apache.org>
 <FECFBB7F-E77D-412E-8E2D-9BACF163BCC9@gmail.com>


On 12/12/2008, at 6:58 AM, Antony Blakey wrote:

> So the guidance is that users must not use document names starting  
> with '_' if they want to avoid astonishment?
>
> The other alternate is to always require the component after the db  
> to be 'special' i.e. document URLs could be
>
>  /db/_/docid%2Fwith%2Fslashes/afile/with/nested/slashes
>
> No special rules required. IMO this example makes clear the cause of  
> the issue.

I got the wrong end of the stick with that idea - this indicates the  
confusion of non-uniformity. Or maybe just the confusion of me :/

IMO design documents should be treated exactly like normal documents.  
Why have any special rules (apart from couch *reacting* to docs with  
an ID starting with '_design')? Uniformity of interface to me suggests  
that there be no special URL handling based on ID.

Regardless of that: given your scheme, do you imagine that the  
following two would be equivalent?

/db/_design/name%2Fwith%2Fslashes/afile/with/nested/slashes
/db/_design%2Fname%2Fwith%2Fslashes/afile/with/nested/slashes

> Also, provide a handler that returns a json document associating  
> filenames with the original name.

And when a file is created in the db directory, write this mapping to  
'filename-mapping.json', in the db directory, so that it's accessible  
even if Couch is down.

Antony Blakey
-------------
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787

Borrow money from pessimists - they don't expect it back.
   -- Steven Wright