From dev-return-1465-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Sat Dec 13 05:19:13 2008 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 50817 invoked from network); 13 Dec 2008 05:19:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Dec 2008 05:19:10 -0000 Received: (qmail 13751 invoked by uid 500); 13 Dec 2008 05:19:22 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 13706 invoked by uid 500); 13 Dec 2008 05:19:22 -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 13694 invoked by uid 99); 13 Dec 2008 05:19:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2008 21:19:22 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates 74.125.44.29 as permitted sender) Received: from [74.125.44.29] (HELO yx-out-2324.google.com) (74.125.44.29) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Dec 2008 05:19:01 +0000 Received: by yx-out-2324.google.com with SMTP id 3so780920yxj.5 for ; Fri, 12 Dec 2008 21:18:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=KlMyrUP2CaH3PLpONA7jTCkQyvYZXfoCpt3B5pW+CWc=; b=PjtYN8tcBlVs+CIRRAFpUaAxZw5wn2x2skO4RvtcDZmdK0ucLHZ0C/3f6nXfu0fDdH npwQgKKIx6/09GUuzN+iUrseD548JoUMVuqdn0gUfmmG8bGB0Xq2g057ZO3BYeOd8v+j Md6cZlWdqUbgQArkkdZ25VFDy9NKRcDCgB5bI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=qfA2UfwdPIMez3V52YQ+wk3Xc06L/bkkSZeDk/oi8zwD7X2/a+y3Y2BgwrG8KiJVnC I+0PVw5qVZ2b30ER2QrzpT89Uu6mazSCzCv56685P4lyS8l8RIcPn/lFVK8ldA8ay/y1 eEQUatwMHzJmsh5zwMwfIWQdjGnj40+XDk6/8= Received: by 10.65.75.2 with SMTP id c2mr3747129qbl.12.1229145519856; Fri, 12 Dec 2008 21:18:39 -0800 (PST) Received: by 10.65.235.11 with HTTP; Fri, 12 Dec 2008 21:18:39 -0800 (PST) Message-ID: Date: Fri, 12 Dec 2008 21:18:39 -0800 From: "Chris Anderson" To: dev@couchdb.apache.org Subject: Re: slash escaping (was 0.9.0 Release) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <0EC6A3E0-15BA-4BBB-A0A3-9ED9D04E3C40@apache.org> <716BFD51-C24A-438E-B9CA-DD0406F80D45@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Dec 12, 2008 at 8:44 PM, Antony Blakey wrote: > > > OK, this code now works for me in a client: I think opening up the character classes of the db and design doc names like this is OK, as it won't effect people who use the current permitted character set. There's no reason this would not work alongside the aforementioned design and attachment path slash rules. Antony, I think you'll find that once you've written the appropriate JavaScript tests for this feature, it'll be hard to resist adding escaping to the Erlang db-name validation code. Once we've got that patch and it works well, expanding the coverage to include design_doc names should be a no brainer. Thanks for taking this up! -- Chris Anderson http://jchris.mfdz.com