> On Nov 13, 2014, at 9:22 AM, Chris Fuentes <[email protected]> wrote: > > What I am primarily interested in doing is separating the replication thread > from the threads that will be performing reads/writes, since the replication > thread becomes very busy from time to time and effectively freezes > interaction with the db.
Replication always runs on a background thread. The CBLReplication object is just a facade that configures the real replication task and reports what it's doing. So it doesn't really matter what thread you start a replication on; it's often best to do it on the UI thread so you can easily use the notifications to drive progress indicators. —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/388C5968-FC04-46E5-85CA-4FCAF6517492%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
