On Mon, Jan 19, 2009 at 12:21 AM, Ulises <[email protected]> wrote: >> maybe a better url would be >> >> /db/_updates?since=200 >> >> _updates is a pretty clear name, and easy to read. > > Could you not do this with an _external? > > (just a thought really) >
I bet you could implement as an _external. The idea behind this is to unify the replication and standard http client interfaces for updates streams, so for instance GET replication (incrementally updating a db that's current as of seq 200) could work via a request like: /db/_updates?since=200&include_docs=full And an _external that wanted to see every (or a subset) of updates (for instance a Full Text Indexer) could use the same mechanism to incrementally maintain an index. Update streams (especially filtered ones) are one of the most powerful tools CouchDB offers. For instance, with filtered streams, you can very easily make docs into persistent state-machines. And the Comet-style requests mixed with client-specified filters makes it very easy to write event-driven browser apps. -- Chris Anderson http://jchris.mfdz.com
