Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D06F4F208 for ; Thu, 28 Mar 2013 01:41:16 +0000 (UTC) Received: (qmail 17622 invoked by uid 500); 28 Mar 2013 01:41:15 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 17575 invoked by uid 500); 28 Mar 2013 01:41:15 -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 17565 invoked by uid 99); 28 Mar 2013 01:41:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Mar 2013 01:41:15 +0000 Date: Thu, 28 Mar 2013 01:41:15 +0000 (UTC) From: "Benoit Chesneau (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (COUCHDB-1737) _changes feed for views MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Chesneau updated COUCHDB-1737: ------------------------------------- Labels: couchdb erlang (was: couchdb erlang gsoc2013) > _changes feed for views > ----------------------- > > Key: COUCHDB-1737 > URL: https://issues.apache.org/jira/browse/COUCHDB-1737 > Project: CouchDB > Issue Type: Improvement > Reporter: Dave Cottlehuber > Assignee: Benoit Chesneau > Labels: couchdb, erlang > > It should be possible to subscribe to view changes the same way we can > subscribe to database changes. This will enable many useful things, > chained map-reduce being a notable one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira