So the scenario would be a liveQuery at app startup, then stop the liveQuery and just monitor replication changes?
On Friday, January 9, 2015 at 3:32:26 AM UTC+3:30, Traun Leyden wrote: > > >> It's called at some point after one or more new documents are added; the >> details are implementation-dependent. I don't know the details of the Java >> implementation; maybe Traun can give details. On iOS I recently optimized >> it so it won't fire more than (IIRC) twice a second. >> >> > Yes, there is some logic > <https://github.com/couchbase/couchbase-lite-java-core/blob/4bf559f0151d58e0bfb77248f3d90f64bc096a91/src/main/java/com/couchbase/lite/LiveQuery.java#L268-L269> > > in place that tries to prevent it from stacking up concurrent livequeries > if one is running while a database update comes in from the db change > listener. > > > -- 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/6ad83dd3-f3b7-4514-ae91-9f1c82932ba2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
