I tried that but: push.Continuous = true;
I also noticed that when using the code:
push.Changed + = (sender, e) => {
var active = == push.Status ReplicationStatus.Active;
if (! active) {
....
}
}
Sometimes not finished syncing and (! Active) = true, at another time
following synchronization.
So my difficulty in knowing who has already been synchronized to avoid the
risk of deleting record that has not been.
What is the guarantee that after synchronization 100% of the documents are
synchronized?
Really I do not see a solution for my case.
And also I do not see the dificudade in providing a property on documents
like: bool isSincronized, as has isDeleted.
Em quinta-feira, 17 de março de 2016 01:16:30 UTC-3, Jens Alfke escreveu:
>
>
> On Mar 16, 2016, at 5:27 PM, Julio Albuquerque <[email protected]
> <javascript:>> wrote:
>
> My android app has a service that is collecting the geographical
> coordinates (latitude and longitude).
> They are very records daily.
> So after sync, I would delete these documents, they will only be used in a
> plant. And the app android these records are not used, only collected.
>
>
> OK, run a push replication, and after it completes or goes idle, you can
> purge the docs.
>
> —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/2f4c339e-dceb-46b5-992b-7a9c9bcc2b3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
