couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson" <jch...@apache.org>
Subject Re: all_seqs stream (was Re: Update notifications including update sequence)
Date Mon, 19 Jan 2009 08:19:02 GMT
On Sun, Jan 18, 2009 at 11:55 PM, Chris Anderson <jchris@apache.org> wrote:
> There are some other update-notification features that could be really
> useful, especially for streaming applications.
>
> Damien's called for a Comet-style connection option for replication,
> which brings really cool affordances on the browser (as well as
> industrial strength replication-streams).
>
> Essentially we're talking about an all_seqs view, with various models
> for consuming it.
>
> /db/_all_seqs?since=200

maybe a better url would be

/db/_updates?since=200

_updates is a pretty clear name, and easy to read.

>
> This would send you the updates that happen after seq 200. With this
> you can hold open a connection, waiting for sequence numbers to
> increment.
>
> You can filter the updates
>
> There is also the possibility of filtering the updates with a
> JavaScript (or other) function posted to the server. It returns true
> or false, passing matching updates along to the client. Updates that
> don't match won't be sent to the client. Using this method you can get
> instant updates of eg: my emails.
>
> This is all Damien's magic, basically things he's mentioned on IRC
> etc. I think Couch is ready for us to start refining the client APIs.
> There's room to do some fairly heavy lifting here.
>
> --
> Chris Anderson
> http://jchris.mfdz.com
>



-- 
Chris Anderson
http://jchris.mfdz.com

Mime
View raw message