Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 47442 invoked from network); 12 Dec 2008 12:34:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Dec 2008 12:34:25 -0000 Received: (qmail 89561 invoked by uid 500); 12 Dec 2008 12:34:37 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 89522 invoked by uid 500); 12 Dec 2008 12:34:37 -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 89511 invoked by uid 99); 12 Dec 2008 12:34:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2008 04:34:37 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [83.97.50.139] (HELO jan.prima.de) (83.97.50.139) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2008 12:34:22 +0000 Received: from [10.0.0.123] (p578b387c.dip0.t-ipconnect.de [::ffff:87.139.56.124]) (AUTH: LOGIN jan, TLS: TLSv1/SSLv3,128bits,AES128-SHA) by jan.prima.de with esmtp; Fri, 12 Dec 2008 12:33:59 +0000 Message-Id: <9E70E1D5-9AE5-41F0-8996-89B56E3F8272@apache.org> From: Jan Lehnardt To: dev@couchdb.apache.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Subject: Re: 1.0.0 wishlist/roadmap Date: Fri, 12 Dec 2008 13:33:27 +0100 References: <20081205163205.GF23179@tumbolia.org> X-Mailer: Apple Mail (2.929.2) X-Virus-Checked: Checked by ClamAV on apache.org On 11 Dec 2008, at 22:12, David Schoonover wrote: > The wishlist is long, but the two missing killer features for me are: > - Native Erlang API You can already use the internal API, but it is going to be changed and polished for 1.0. > - DB Sharding (CouchDB)-client sharding is possible today. DB partitioning transparent to a client is not planned for 1.0. Cheers Jan -- > > > On Thu, Dec 11, 2008 at 4:02 PM, Antony Blakey > wrote: >> >> On 12/12/2008, at 7:28 AM, Damien Katz wrote: >> >>> >>> On Dec 11, 2008, at 3:43 PM, Chris Anderson wrote: >>> >>>> On Fri, Dec 5, 2008 at 2:30 PM, Damien Katz >>>> wrote: >>>>> >>>>> Yes yes yes! This is exactly how it should work, pull all the >>>>> docs in a >>>>> single http request and also record the last seq num. Then later >>>>> incrementally pull new changes using the seq num, lather rinse >>>>> repeat. >>>>> Restore by POSTing the docs in bulk updates. >>>>> >>>> >>>> With the same view (_all_docs_by_seq with super_include_docs), >>>> could >>>> recipient-triggered replication be accomplished in a single HTTP >>>> request? This might speed up replication a bunch as well. >>>> >>> >>> I'm thinking of removing the _all_docs_by_seq HTTP view and >>> replacing it >>> with something that will allow for more flexibility and also allow >>> for Comet >>> like events, by providing a filter function that finds documents >>> that meet a >>> criteria, and to be notified immediately when new documents are >>> saved that >>> meet that criteria. This is meant to be used by the replicator and >>> external >>> indexers, but to also try to make it be like a regular view and >>> while >>> supporting all the other stuff is pointlessly complex. >> >> Mmmm, tasty! >> >> Antony Blakey >> -------------------------- >> CTO, Linkuistics Pty Ltd >> Ph: 0438 840 787 >> >> Success is not the key to happiness. Happiness is the key to success. >> -- Albert Schweitzer >> >> > > > > -- > LOVE DAVE >