incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joscha Feth <jos...@feth.com>
Subject Re: atomic/concurrent update_seq for _changes
Date Sun, 27 Dec 2009 20:44:43 GMT
On Sun, Dec 27, 2009 at 21:36, Troy Kruthoff <tkruthoff@gmail.com> wrote:
> I have an app that gets data from a view and then monitors _changes for
> updates.  Currently it:
>
> 1)  Gets the update_seq from the database
> 2)  Gets data from a view
> 3)  Connects to _changes since updae_seq from #1

I am doing exactly the same in my application and the gap between #1
and #2 also worried me - a special header sounds like a feasible
solution and I can't see any downside besides the few bytes of
overhead in the header for each request.

regards,
Joscha

Mime
View raw message