The replication model is such that for every connected graph of peers, all peers in that graph will update to the same up-to-date state. This is what they call "eventual consistentcy".
It's like in bittorrent, you don't have to worry about the clients with full copies of the file somehow losing data; the replication data is versionned, so your peers will only replicate "forward" in time, not backwards. Sent from my iPhone On 2011-04-05, at 1:36 PM, Zdravko Gligic <[email protected]> wrote: > Hi Folks, > > Are there any large implementations of CouchDB peer-to-peer > replications or even smaller open source samples? Actually, the piece > that I am mostly interested in is at the application/design end of how > to go about implementing the "traffic cop" for a use case where > everyone is eventually synchronized with everyone else. > > Given a large number of peers that one could replicate to/from, is > there anything within CouchDB that can be "posted centrally" to know > how up to date anyone is, so that badly out of date peers are > replicate to/from the more up to date ones, instead to/from each > other? What else should I ask, if I knew better ;?) > > Thanks, > Zdravko
