> On Aug 7, 2014, at 5:33 PM, Deep Eddie <[email protected]> wrote: > > • Does this socket get established as soon as i call pull() from the > iOS client?
It's opened as soon as the pull replication goes online, yes. > • And the socket stays open foreever from that time onwards? A continuous pull replication keeps the socket open. A non-continuous replication stops as soon as all the current changes from the server have been downloaded. > • What happens to the socket when the app is minimized or in the > background? Replications pause when the app is backgrounded. The socket will be closed, and re-opened when the app next activates. > • What kind of factors do i need to consider at the F5 level to be able > to scale appropriately? I can't personally answer that, because I'm not a server expert and don't know much about load balancers. > • And finally, is there a way to indicate at the client side to not > keep the connection open permanently? Any drawbacks of this? I have a > shared loadbalancer and dont want to hog on all available sockets! Set a polling interval on the replication object. The drawback is increased latency of getting updates from the server. —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/64EF6EE6-8B52-4313-B552-D89857EF6758%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
