Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 2301 invoked from network); 18 Mar 2009 02:27:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Mar 2009 02:27:25 -0000 Received: (qmail 83480 invoked by uid 500); 18 Mar 2009 02:27:19 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 83443 invoked by uid 500); 18 Mar 2009 02:27:19 -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 83432 invoked by uid 99); 18 Mar 2009 02:27:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2009 19:27:19 -0700 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 209.85.132.245 as permitted sender) Received: from [209.85.132.245] (HELO an-out-0708.google.com) (209.85.132.245) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2009 02:27:11 +0000 Received: by an-out-0708.google.com with SMTP id b2so238400ana.5 for ; Tue, 17 Mar 2009 19:26:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=VER8sxkkIsyH71zRxGYBQ599bvH8wU1ApxOqUOmYdac=; b=J6CTBGDtzRU1KSkvLS76HeEkT+SqPaPd+3T7Bu31L6BYnWsAFDJk3pA8KyaeQHytUp HnQac57r1EOJY7fvmyd8segAMLLD/P7TIvcRdvJuushUEsTblYtD8/1e/DaIYmVKtL8F wZIzitbCKrI6se0s14pZCIBZRx6LL/TLx7NYA= 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 :content-transfer-encoding; b=VuxS9hY5Dd18W58+kp+5ese2RkCSwzepuPtZ6/DrRLXDDKTJk7YNX7TwG9DTcEaPMG +h7nFhCHJybcS+4VGZdqzANFDjicRtFEO1jpXmXCDo4XzkHXJpbhy2wLtlwQeUWkAu0F ppIbCmDqWV2qKbMTnOk7+gb8MIZgagrQ6f8xM= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.142.141.21 with SMTP id o21mr264091wfd.276.1237343209583; Tue, 17 Mar 2009 19:26:49 -0700 (PDT) In-Reply-To: References: <64a10fff0903171343y21b66103nfd2581ae6057063d@mail.gmail.com> Date: Tue, 17 Mar 2009 19:26:49 -0700 X-Google-Sender-Auth: 69bdfc89c2dfb58b Message-ID: Subject: Re: Trying to see if CouchDB is right for our project... From: Chris Anderson To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Mar 17, 2009 at 7:19 PM, Daniel Friesen wrote: > > Counter-proposal, I have an idea for document references in CouchDB. It's > completely backwards compatible, usable in a number of cases, and should > theoretically perform quite well. > > I've drafted up a big explanation, think it would be a good idea to put it > on the Wiki and ping the dev list? > Please do. I'm curious to see what you've got. Don't be surprised if it's not accepted (at least right away). CouchDB has a pretty strong idea of what it's trying to accomplish, and there a ton of work to be done before 1.0. But it could just be that you've got something we haven't thought of or discussed, that turns out to be a good fit. No way to know without bringing it up! Also, there's lots of room in the implementation for alternate view engines, so if you were to code something up, and get people using it, it'd be fairly easy to fit into the codebase. Cheers, Chris -- Chris Anderson http://jchris.mfdz.com