From dev-return-4378-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Tue May 26 10:15:17 2009 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 14805 invoked from network); 26 May 2009 10:12:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 May 2009 10:12:57 -0000 Received: (qmail 30866 invoked by uid 500); 26 May 2009 10:13:10 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 30795 invoked by uid 500); 26 May 2009 10:13:09 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 30785 invoked by uid 99); 26 May 2009 10:13:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 May 2009 10:13:09 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [91.189.90.139] (HELO adelie.canonical.com) (91.189.90.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 May 2009 10:12:57 +0000 Received: from hutte.canonical.com ([91.189.90.181]) by adelie.canonical.com with esmtp (Exim 4.69 #1 (Debian)) id 1M8td5-0000Tg-G6 for ; Tue, 26 May 2009 11:11:31 +0100 Received: from 87-251-59-67.lombox.customer.bit.nl ([87.251.59.67] helo=[192.168.0.133]) by hutte.canonical.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1M8td5-0003xO-CI for dev@couchdb.apache.org; Tue, 26 May 2009 11:11:31 +0100 Message-ID: <4A1BC052.8060802@canonical.com> Date: Tue, 26 May 2009 12:11:30 +0200 From: eric casteleijn User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: dev@couchdb.apache.org Subject: Re: Document update notifications References: <20090408110546.GA26996@gera-laptop> <20090408181520.GA9578@gera-laptop> <9AE71556-202B-4EFA-8EED-8C54E326B48B@apache.org> In-Reply-To: <9AE71556-202B-4EFA-8EED-8C54E326B48B@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org >>> 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'm working on it and even I can't say when :) Too much stuff pops up > that's out of my control, so I don't give completion estimates any more. > > But I will say it's my highest priority development task right now. I'm sorry for asking again, but this feature (or rather, getting rid of the update notifiers) is turning out to be more and more critical to us. Is there *anything* we can do to help this along? If so, please let me know, on or off list. -- - eric casteleijn http://www.canonical.com