Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 73787 invoked from network); 26 Oct 2010 03:39:05 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Oct 2010 03:39:05 -0000 Received: (qmail 33251 invoked by uid 500); 26 Oct 2010 03:39:04 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 33161 invoked by uid 500); 26 Oct 2010 03:39:03 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 33151 invoked by uid 99); 26 Oct 2010 03:39:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Oct 2010 03:39:03 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kowsik@gmail.com designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bw0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Oct 2010 03:38:57 +0000 Received: by bwz6 with SMTP id 6so3631178bwz.11 for ; Mon, 25 Oct 2010 20:38:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=8FgxvJH9oZZLbKsDMxPfNSNZ3Zil7BrBiL13Bd2VdTo=; b=jHaIL1X7mnVi0oaQ+XLgdEDih1wRaXR1GDmKCRzxYngauaXl6dlLvabusKS9yE6sb+ 8rMY0QhS1/N3fU9w0IBLLr1XQomclEeGbycbunjHgzONmqDYw9t+0yCmHGV61GqjfKzF 4dNDJNw47yemn4V6k7O9ogP1p1ZC9KPxhqNuM= 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=a5GOBRyzsyH2ybSytLbLJrN591n3alt6Mq/MOu6pKfNE1rQGAN+kFd7sEE2zdnCGx+ KIZYLhcV7tYIxwT6xDZGeiYChnF6XKcCXpAA5qkaS1Ue/1FqI2vwHqr2Ooq3puQzIxhv siNDyP4DPeE6mVsCgPvQFn/VEAqUSXWQIiFgo= MIME-Version: 1.0 Received: by 10.204.59.69 with SMTP id k5mr5734432bkh.195.1288064316673; Mon, 25 Oct 2010 20:38:36 -0700 (PDT) Received: by 10.204.152.129 with HTTP; Mon, 25 Oct 2010 20:38:36 -0700 (PDT) In-Reply-To: <7F47D1F3-9D05-4C7A-896D-8EA41D6B10F7@apache.org> References: <7F47D1F3-9D05-4C7A-896D-8EA41D6B10F7@apache.org> Date: Mon, 25 Oct 2010 20:38:36 -0700 Message-ID: Subject: Re: Questions about changes feed From: kowsik To: user@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Oct 25, 2010 at 7:57 AM, Adam Kocoloski wrote: > On Oct 24, 2010, at 10:10 PM, kowsik wrote: > >> I have a few questions about the _changes feed. >> >> 1. How many changes are kept around for each DB? Obviously, not >> everything, but is it the last 100, 1000 or some other configurable >> limit? > > The most recent edit of each branch of every document is kept around forever, or until a new edit on that branch occurs. Thanks Adam. A follow up observation (enhancement request really): I like the way the filter code gets the document so it can use the req.query to only push certain notification to certain clients. Unfortunately when a document gets deleted all I get is something like this: {"seq":389,"id":"8f8bb53dbf8eb9be81923fea21072386","changes":[{"rev":"2-30b513fc78ad7eadd4db4b7f87591338"}],"deleted":true} It would be nice to have the actual doc be part of this so that the filter can be more intelligent in its routing decision. For example, only notify certain interested clients about the deletion. Thanks, K. --- http://www.pcapr.net http://twitter.com/pcapr http://labs.mudynamics.com