Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <31300881.35621277366569961.JavaMail.jira@thor>
Date: Thu, 24 Jun 2010 04:02:49 -0400 (EDT)
From: "Benoit Chesneau (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-360) Add global _changes feature
In-Reply-To: <311677927.1243294065533.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882085#action_12882085 ] 

Benoit Chesneau commented on COUCHDB-360:
-----------------------------------------

I woud like to refresh this ticket. 

It's useful sometimes to have global db changes (db created, deleted) for external apps without using intenal update notififier and also more powerfull than diffing _all_dbs results. Ex of usages :

- monitoring dbs (and add db monitored on the fly)
- start replication on creation
...

Anything against ?

> Add global _changes feature
> ---------------------------
>
>                 Key: COUCHDB-360
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-360
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: HTTP Interface
>            Reporter: Robert Newson
>         Attachments: db_changes.patch, db_changes2.patch, db_changes3.patch, db_changes4.patch, global_changes.patch, global_changes.patch
>
>
> Add a global version of _changes to allow monitoring of changes to all databases. It does not need to include details of the change as clients of this interface must track update sequences for each database anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.