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 paul.joseph.davis@gmail.com
 designates 209.85.132.249 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:content-transfer-encoding;
        b=imOgs4QUSf0UL1K+ndUqW77nWwnGkCQ4K1hEi7S09u/TjrN9/oYLAOkFbO2FiGseI5
         K2pyvtYSK31zb9p9JppHlaqMcFMGFeLltJezqqZ4oEbBJwtfRKXbFGo3lqwiMm7Dvk+R
         h0L6KlY9mLH98uTxxp0niXlg5mjgj6vsLc1F8=
MIME-Version: 1.0
In-Reply-To: <20090408181520.GA9578@gera-laptop>
References: <20090408110546.GA26996@gera-laptop>
	 <e2111bbb0904081101l77897434hfde592dba112b8bd@mail.gmail.com>
	 <20090408181520.GA9578@gera-laptop>
Date: Wed, 8 Apr 2009 14:44:21 -0400
Message-ID: <e2111bbb0904081144m94b33eck1da0420758e9a540@mail.gmail.com>
Subject: Re: Document update notifications
From: Paul Davis <paul.joseph.davis@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Wed, Apr 8, 2009 at 2:15 PM, Devendra Gera <gera@theoldmonk.net> wrote:
> Hi Paul,
>
> Thanks for taking the time to review the patch.
>
> On Wed, 08 Apr 2009, Paul Davis wrote:
>
>> Gera,
>>
>> That looks like a solid patch, but unfortunately I think that the
>> comet notification will end up superseding the functionality. The
>> basic ideas of the comet framework are to post a JavaScript function
>> to the server to allow clients to filter db updates. I'm pretty sure
>> this is under active development so stay tuned for updates.
>
> Would the comet notifications supersede the (currently implemented) db
> update notifications as well? Are there any estimates as to when that
> would come around.
>

Pretty sure the idea is to replace the current system's functionality.
I'm not sure if that means update_notification will go away or not,
but from what I gather on the expected use cases it'll be a "new code
should use comet" type of situation. As far as estimates, I'm not
sure. I don't have too much knowledge on the current status, just that
there was work being done on some necessary bits. Keep an eye on dev@
and you'll be up to date as things start building up.

> I guess, what I'm trying to ask is that does the patch make sense as in
> interim solution?
>

If you mean in trunk, I'm not sure but I doubt it. If for no other
reason than if we added such a feature to trunk it'd be a signal that
we intend to support it for a very long time when we're already acting
on plans to replace it.

> If not, we'll just keep using the patch internally (and offer it
> out-of-tree) while waiting for the superseding functionality.
>
> Thanks,
> --gera.
>
>

HTH,
Paul Davis