on iOS. On Friday, 8 August 2014 14:17:16 UTC+1, Arash Ashrafi wrote: > > > A one-shot replication, very often, needs to be FOLLOWED by some other > action WHEN finished. > > In order to be able to do that, a reliable mechanism is required to say > that: > 1. it is stopped > 2. how has it stopped (successful, interrupted, neverStarted etc.) > > At the moment, by observing replication change notifications, the > following cases are not easy to handle: > 1. If you start the replication with no network connection, it sends only > one notification with "Offline" status and gets stuck (never goes to > "Stopped") > 2. If network connection get's lost in the middle of replication, it keeps > sending "Offline" replication notifications, strangely with "completed > changes count" being increased and going above "changes count". > 3. If network connection get's lost in the middle of replication, it stops > at some point, but there is no control over how long it should wait till it > gives up trying. > > Suggestions: > a) Improving the one-shot replication mechanism to guaranty that it always > stops at some point (goes to "Stop" status) > b) Providing some API for one-shot replications to provide a time-out > setting (so that if it can not progress for any reason, it goes to "Stop" > status after that time) > c) Having a final replication status property, to access after replication > has stopped, in order to find out the out come of the replication. > > > >
-- 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/c43934ac-f6cb-4935-a1a2-df6b006093db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
