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.
On Thursday, November 13, 2014 11:48:21 AM UTC-5, Chris Fuentes wrote: > > According to the most recent docs > <http://developer.couchbase.com/mobile/develop/guides/couchbase-lite/native-api/database/index.html>, > > (using 1.0.3) > > If your app uses Couchbase Lite on multiple threads, then on each thread > (or dispatch queue) it must: > > - Create a new CBLManager instance. If you use multiple threads, do > not use the sharedInstance. > - Use only objects (Databases, Documents, ...) acquired from its > Manager. > - *Not* pass any Couchbase Lite objects to code running on any other > thread/queue. > > Does this mean that a set of replication objects must be created for each > thread as well, even if they're all pointing to the same sync gateway > instance? > -- 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/b0c2f555-8adb-4bfc-af67-7397e12ac24f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
