On Jan 21, 2016, at 4:17 AM, Denis Howlett <[email protected]<mailto:[email protected]>> wrote:
1. We POST a _replicate request to CBL with Cloudant as the source, CBL as the target and a filter to use. 2. With a poor connection, this replication sometimes takes more than 5 minutes to return --> I was expecting it to return immediately with a session_id and ok: true indicating that the replication had been kicked off. Continuous replications send a response immediately; one-shot replications don’t send a response until complete. (That’s not our idea, it’s how CouchDB implemented it and we’re going for compatibility.) We've had a case just now where we seem to have 6 documents of the 7 we were expecting. That shouldn’t happen unless the connection is lost. What happens if the connection is dropped during a replication? Does it just add/update the documents it's got so far or is it "transactional" (i.e. all or nothing)? The puller adds docs as it goes. There is no notion of a transaction. How does it work if you then re-sync? Is it able to work out that the extra document should be synced? Yes, it keeps track of how far it got last time, and will pick up from there on the next replication. —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/A3E10663-4BDD-438A-BA51-D4D243AD70C7%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
