> On Sep 2, 2014, at 2:31 PM, Traun Leyden <[email protected]> wrote: > > A possible solution to this is to have a field which tracks this, and > something that is listening to the sync gateway changes feed would update > that field.
That will work, but it'll result in a lot of extra replication traffic and bigger revision trees. It doesn't seem worth it, IMHO. We need better replication progress monitoring APIs. It's possible to tell whether a doc has been pushed by comparing the push replicator's checkpoint sequence number with the (local) sequence number of the doc's latest revision. But there's no public API exposing the replicator's checkpoint. We could add a property to make that checkpoint accessible, but it seems kind of a weird low-level thing. I guess a higher-level API might look like -[CBLReplication hasPushedDocument: (CBLDocument*)doc]. —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/006EC1C3-8766-498C-9CDC-E3315BF4993F%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
