> On Aug 8, 2014, at 6:17 AM, Arash Ashrafi <[email protected]> wrote: > > 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.
These sound like things you can implement yourself, if you need them. For instance your client can keep its own timer and stop the replication if it doesn't go online within that time interval. Are there any features you need that you're finding impossible to implement? —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/079A4CC7-B604-464F-99E3-02E6DDCC4000%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
