> On Apr 17, 2015, at 10:41 AM, Victor Fernandez <[email protected]> > wrote: > > My problem is that only when is active the method replicationProgressP2p the > peer to peer connection works great, but when the replication becomes > inactive despite I make some local database changes the method > replicationProgressP2p turns active only after several time, in many > scenarios takes more than a minute.
I think what you’re saying is: 1- the initial replication catches up and the status of the push replicator goes from Active to Inactive 2- you make a local change 3- the push replicator doesn’t push the change immediately, instead it takes a minute or longer Correct? I’m wondering what the exact status changes are. Could you add logging to your notification handler to log the status property as well? The only explanation I can think of is that for some reason the replicator goes to Offline, meaning it doesn’t think the other device is reachable. In that case it won’t try to replicate again until the device shows up as reachable again. —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/547A4DA6-EB3D-4477-9D50-660F1CF9BF04%40mooseyard.com. For more options, visit https://groups.google.com/d/optout.
