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 randall.leeds@gmail.com
 designates 209.85.216.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=S8Tq2FtcaGlo63+HYFYkSXNE7Oqx7jQTkfNNeP01ZGAi/xFT7/JosFV/frcRUexdlt
         6XFWbjMbYw5JpK3BYFm1zFe2LoBmEKXzyE0famNgCbnjYBl5jWXOKb7zJSr4Jiw2gPd2
         wP5j3vhY8xgCO5tjtGySSakksJe4nDHTd3nJk=
MIME-Version: 1.0
In-Reply-To: <AANLkTikZ0aYZim01gEFaQOeXgZYcxST074sa5yvF6D_q@mail.gmail.com>
References: <AANLkTin=PhtkbQX7SJSoDAgcs3EJ+VZ_BBsKb2fukwnr@mail.gmail.com>
	<AANLkTinte65oBBY1iDhjaV2e4QOrHAs60d0ZBqPb+Hst@mail.gmail.com>
	<AANLkTik1E-NzesS3hxO7zdtSdtM2eVscpcSULOud11Jj@mail.gmail.com>
	<AANLkTimfXM9YM1+TLRuF_SgD_LRhw+Z20vC9bmfg7ikv@mail.gmail.com>
	<AANLkTinF3Ypzk5ujTwD5mr=8v7sJcKkXbTjBAJ_GEDMC@mail.gmail.com>
	<AANLkTinbuVM+bK3=KgqcckgoJM9n1MjRfO3eUW0mmNWg@mail.gmail.com>
	<AANLkTinobdPn+k8fWFmS3OxDBQLALfn=x+9GkLaicsvP@mail.gmail.com>
	<AANLkTintbE3qZkK4c3Xz---fU35tnEh22r2Hib+9+MoJ@mail.gmail.com>
	<AANLkTi=kazQfTsYicZbiKTcqovy9d4Fg5=SswTdAW627@mail.gmail.com>
	<AANLkTinVafxTLYjvyEPRgRPgrwG1a2hzOuBRuo-xGOzM@mail.gmail.com>
	<AANLkTikZ0aYZim01gEFaQOeXgZYcxST074sa5yvF6D_q@mail.gmail.com>
Date: Mon, 2 Aug 2010 11:35:31 -0700
Message-ID: <AANLkTimDRfYfV3ZhOrD69VoWom0tCbr+c93zVwWkQ2yV@mail.gmail.com>
Subject: Re: Proposal for changes in view server/protocol
From: Randall Leeds <randall.leeds@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

On Mon, Aug 2, 2010 at 11:29, Jason Smith <jhs@couch.io> wrote:
> On Tue, Aug 3, 2010 at 00:21, Randall Leeds <randall.leeds@gmail.com> wrote:
>
>> I'm 100% in favor of more radical js improvements like emonk.
>>
>> However, toward Jason's comment, what do you all think of exposing a
>> saveDoc
>> function instead?
>
>
> I am eager to process form submissions from web browsers. Whatever makes
> that possible would be just fine.
>
> I think the only significant critique about this is that the view server is
> blocked, so what would process the validation functions? Chris said that
> that's not a fatal flaw, you just spin up more view servers.

I think the view server is blocked either way with the current protocol, no?

Either way we're waiting for a response from couch to call back into
JS, it's just whether we're calling the original function or the
continuation.
I don't have a strong preference either way, but I do slightly favor
the callback continuation as a mild style preference.

In either case, do we have to add some new response format so the
query server can say "Hey call me again and tell me what to do with
this result?"
In other words, both of our suggestions can work on top of the same
change that needs to happen to the view server line protocol, so you
can code up either one and we can settle on what it should look like
to people writing update handlers later, no?