couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Anderson <jch...@apache.org>
Subject Re: Document update notifications
Date Sun, 31 May 2009 07:59:17 GMT
http://jchrisa.net/drl/_all_docs_by_seq also has gaps, see 371 in here.

The coolest thing that could happen to _changes right now is a
multi-part mime encoding so we could stream attachments on the same
connection as documents for true continuous replication.


On Sat, May 30, 2009 at 9:29 PM, Paul Davis <paul.joseph.davis@gmail.com> wrote:
> On Sat, May 30, 2009 at 11:48 PM, Randall Leeds <randall.leeds@gmail.com> wrote:
>> On Tue, May 26, 2009 at 11:22, Chris Anderson <jchris@apache.org> wrote:
>>>
>>> There are other parts of the story we could add but haven't. For
>>> instance, it should be possible to do a long poll on a particular
>>> document URL if you are waiting for it to be modified. Also,
>>> replication should be able to run against the _changes API instead of
>>> _all_docs_by_seq, although I'm not sure that's crucial for your use
>>> case.
>>>
>>> I hope that give enough clarity for you.
>>>
>>> Chris
>>
>>
>> I just took a glance at _changes. When a compaction is performed and then a
>> fairly old sequence number is requested as the "since" sequence number, are
>> there simply holes in the seq count where old revisions used to be?
>>
>
> Unless something major has changed, yes there are holes. Ie, if a
> document update results in a document being update sequence id N, then
> you update that document again and it becomes update sequence N+1,
> then the previous update sequence (N) no longer exists.
>



-- 
Chris Anderson
http://jchrisa.net
http://couch.io

Mime
View raw message