On Sat, May 30, 2009 at 11:48 PM, Randall Leeds <[email protected]> wrote: > On Tue, May 26, 2009 at 11:22, Chris Anderson <[email protected]> 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.
