Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of space.ship.traveller@gmail.com
 designates 209.85.220.49 as permitted sender)
Message-ID: <53C277CE.9000309@gmail.com>
Date: Mon, 14 Jul 2014 00:13:02 +1200
From: Samuel Williams <space.ship.traveller@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: dev@couchdb.apache.org
Subject: Re: CouchDB 2.0: breaking the backward compatibility
References: 
 <CAHdjipKcNRMoYSNprk06X_vpTmniS0EQBDjfhO-Path5jqrbqg@mail.gmail.com>
In-Reply-To: 
 <CAHdjipKcNRMoYSNprk06X_vpTmniS0EQBDjfhO-Path5jqrbqg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


On 13/07/14 23:47, Alexander Shorin wrote:
> Our view server is compiles functions on each view index update
> instead of reusing inner cache. This is because of out-dated protocol:
> others design function are works differently from views. While it's
> good to change and improve query server protocol completely, this task
> requires more time to be done. We should have a least plan B to do
> small steps in good direction.
As already suggested, here is my proposal for 2.0 view/query server:

https://docs.google.com/document/d/1JtfvCpNB9pRQyLhS5KkkEdJ-ghSCv89xnw5HDMTCsp8/edit

I welcome people to suggest improvements/changes/ideas.

Kind regards,
Samuel