I have implemented the timer already. Those were just suggestions for improvement.
Apart from the time-out, when replication goes to "Stopped", there is not a clean way to say HOW the replication ended. Did it finish the job and stopped? Did it get interrupted? Did it get stuck for some reason? Did it manage to connect to remote server at all? And, when the replication is stopped with its "stop" method, I believe it makes sense to send a notification with status: "Stopped". It doesn't at the moment. Anyway, as you said, non of these are things impossible to implement by ourselves. For example, we can use lastError property to some extent for that. -- 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/eb916178-2637-4701-bce0-0065ed8fb6f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
