On Mon, Nov 5, 2012 at 7:08 AM, Dustin Sallings <[email protected]> wrote: > Benoit Chesneau <[email protected]> > writes: > >> i am with my laptop in an office. Start a replication with a remote node. >> >> my laptop get an ip/port from dhcp, the remote has an ip / address. >> >> I'm moving in another office. connect to the dhcp. there is also a >> remote node with same ip/adress port than the first one but for >> confidentiality i shouldn't replicate to it. It is expected that the >> replication stop at this point. >> >> This scenario is more obvious if we take the example of someone gong >> from one stair to the other using the wifi. > > IMO, it makes more sense to optimize for the case where people don't > create two servers with the same name and/or IP address in two different > networks a single user is likely to connect to, but where the two > servers have different replication policies that should be handled > implicitly and SSL/TLS is not used to confirm the correct server is in > place. > > Mysteriously running either two or zero replicas on my laptop for a > single configured backend would *almost* be excusable with your > justifications if it didn't fix itself when I restarted CouchDB. > > -- > dustin > Just ask around you how many people aren't changing the default port of couchdb and pur their servers in usual ip ranges you expect from a server. Imo a port change is a significant event.
- benoit
