Return-Path: 
 <dev-return-22699-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org>
X-Original-To: apmail-couchdb-dev-archive@www.apache.org
Delivered-To: apmail-couchdb-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3B770D7C2
	for <apmail-couchdb-dev-archive@www.apache.org>;
 Sat, 21 Jul 2012 16:24:50 +0000 (UTC)
Received: (qmail 55694 invoked by uid 500); 21 Jul 2012 16:24:49 -0000
Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org
Received: (qmail 55653 invoked by uid 500); 21 Jul 2012 16:24:49 -0000
Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@couchdb.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@couchdb.apache.org>
List-Post: <mailto:dev@couchdb.apache.org>
List-Id: <dev.couchdb.apache.org>
Reply-To: dev@couchdb.apache.org
Delivered-To: mailing list dev@couchdb.apache.org
Received: (qmail 55644 invoked by uid 99); 21 Jul 2012 16:24:49 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Jul 2012 16:24:49 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of space.ship.traveller@gmail.com
 designates 209.85.212.176 as permitted sender)
Received: from [209.85.212.176] (HELO mail-wi0-f176.google.com)
 (209.85.212.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Jul 2012 16:24:43 +0000
Received: by wibhn17 with SMTP id hn17so1071264wib.5
        for <dev@couchdb.apache.org>; Sat, 21 Jul 2012 09:24:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=XEYylpALUQZwJQ+FZdQ5vb9Mq7HAFKM7Gb6vz2JdYSg=;
        b=JzT7zS+NgI5w2sRXoMROEONgXmHubzQk3Aa1AnESBvHBu4Y+0HQXh8BqRGs0uvSd3+
         ZT9ADjG530/7C0+TvNvxxr9TJkB7YP1xvst6LpcllV4wZMiOwenMoAJrV8EfeJ1uautG
         6VYg8lsH3oB7TEToueN2A0Ajz514Hw8aeAclDfPKLbvIEciKzRN5CLUd0ZDPSyRh/hdI
         4nMrAX3I9KwknO1azOUb2i6qnAMtxS+X9nnZK13bSl6Z1W9tSQeMa9lOjm8WQMjufQtW
         LaSIZO36CVKdcNbmklfiYqVzeLIHOFMg7fbs/P5jw6AC/W8ylp486mKWBURCiFVbJoxc
         lHBg==
MIME-Version: 1.0
Received: by 10.180.84.104 with SMTP id x8mr34622526wiy.20.1342887862768; Sat,
 21 Jul 2012 09:24:22 -0700 (PDT)
Received: by 10.216.245.73 with HTTP; Sat, 21 Jul 2012 09:24:22 -0700 (PDT)
In-Reply-To: 
 <CAHdjip+TjE7TH_Y-q66tfwSktQzBSQLPYSegnb9=jd3XDL3v4A@mail.gmail.com>
References: 
 <CAHkN8V_n0rwwyP2KvHGO4rSCASn+uFfeHHFHn3zA1cgqxfa1mA@mail.gmail.com>
	<CAHdjip+TjE7TH_Y-q66tfwSktQzBSQLPYSegnb9=jd3XDL3v4A@mail.gmail.com>
Date: Sun, 22 Jul 2012 04:24:22 +1200
Message-ID: 
 <CAHkN8V9uF6tt-8CW3-VNjWM=nty=xEYN9+VRh5_YxtU4jchWXA@mail.gmail.com>
Subject: Re: "ddoc" protocol for query server?
From: Samuel Williams <space.ship.traveller@gmail.com>
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=f46d043bd75808950804c559728e

--f46d043bd75808950804c559728e
Content-Type: text/plain; charset=ISO-8859-1

Hi Alexander,

Thanks for the details, that is really helpful.

It might be good if documentation was updated.

W.R.T. design documents, why isn't it used for view related functions,
since it seems to include all the code for that purpose? Is it due to
efficiency? Is design document the future of the query server structure?

Kind regards,
Samuel

On 22 July 2012 03:52, Alexander Shorin <kxepal@gmail.com> wrote:

> Hi Samuel.
>
> I'd attempt to update query server documentation, but it was stopped
> at point "not readable" |:
> About "ddoc" command: yes, currently it is in use for any design
> functions except views. It work in two phases:
> 1. It delivered copy of design document to query server with message
> ["ddoc", "new", "<<ddoc-id>>", {<<ddoc-json-object>>}] to let query
> server cache it. For each ddoc changes in CouchDB his new version also
> been sent to query server processes.
> 2. It ask query server which function to run by message ["ddoc",
> "<<ddoc-id>>", ["path", "to", "function"], [<<function arguments>>]].
> First element of function path points to "what design function to
> execute" (shows,lists,filters,updates etc.) which also called as "ddoc
> cmd".
>
> The best documentation is the source code for now:
> https://github.com/apache/couchdb/tree/master/share/server
>
> --
> ,,,^..^,,,
>
>
> On Sat, Jul 21, 2012 at 7:27 PM, Samuel Williams
> <space.ship.traveller@gmail.com> wrote:
> > Hi,
> >
> > I've been reviewing various query server implementations and some seem to
> > have a "ddoc" command. I'm wondering if this is still used in CouchDB 1.2
> > and if so, where is the documentation?
> >
> > If not, why not?
> >
> > Kind regards,
> > Samuel
>

--f46d043bd75808950804c559728e--