Documented high availability a bit more

Dache.Client/Client.Example.config

@@ -6,7 +6,12 @@
         <section name="cacheClientSettings" type="Dache.Client.Configuration.CacheClientConfigurationSection, Dache.Client"/>
     </configSections>
 
-    <!-- Cache Client Settings -->
+    <!-- Cache Client Settings
+         hostReconnectIntervalSeconds: the interval in seconds at which to try reconnected to a disconnected cache host
+         hostRedundancyLayers: the number of servers that should duplicate data. EXAMPLES: If you have 10 servers and set this to 0, you'll 
+                               have 10 cache host buckets with 1 server each (no redundancy). If you have 10 servers and set this to 1, 
+                               you'll have 5 cache host buckets with 2 servers each (doubly redundant and doubly available). Use this to 
+                               guard against Dache host server shutdowns or crashes -->
     <cacheClientSettings hostReconnectIntervalSeconds="10" hostRedundancyLayers="0">
         <!-- Custom logging is optional, but this is how you'd implement it. Your custom type must implement Dache.Client.Logging.ILogger -->
         <customLogger type="My.Custom.Logger, My.Custom" />

README.md

@@ -52,7 +52,7 @@ VERSION INFORMATION
 1.4.0 - THE FASTER, BETTER, STRONGER BUILD!
 ------------------
 
-- HIGH AVAILABILITY! You can now configure Dache to use > 1 cache host per cache fragment/bucket. This allows for redundancy in the case of cache server failure!
+- HIGH AVAILABILITY! You can now configure Dache to use > 1 cache host per cache fragment/bucket. This allows for redundancy in the case of cache server failure! To utilize this, adjust the `hostRedundancyLayers` setting in the dache client `.config` file.
 
 - FASTER BETTER COMMUNICATION! SimplSockets rewritten for much more efficient communication. Also streamlined the Dache low level TCP syntax.