ravendb/ravendb — pull request #387 by dangerwheeler (2011-10-10 14:23:23+00:00)
Title: Optionally separate client failover configuration from server replication configuration

ReplicationInformer checks for Raven/Replication/FailoverDestinations first. If not present, it uses Raven/Replication/Destinations (and thus preserves compat with existing configurations).

If we go with this route, it may make sense to do some renaming in ReplicationInformer to indicate that it's focused on client failover behavior, not server replication behavior.

Also, I struggled to a really simple way to unit test just the ReplicationInformer failover configuration. Does it make sense instead to add a test in Raven.Replication.Tests?