X-Git-Url: https://git.m6w6.name/?a=blobdiff_plain;f=docs%2Fmemcached_behavior.pod;h=00d762825d2da1f4757e2000b7843820843ba11a;hb=921abbe1906e77cc18cbe8859bc5afe9494d780e;hp=26a35ec9a1b278b0348fda118c2c76713bad70ac;hpb=b10a03e4afb5514f1c86f5c75b9bfc7d46ce49b4;p=m6w6%2Flibmemcached

diff --git a/docs/memcached_behavior.pod b/docs/memcached_behavior.pod
old mode 100755
new mode 100644
index 26a35ec9..00d76282
--- a/docs/memcached_behavior.pod
+++ b/docs/memcached_behavior.pod
@@ -1,6 +1,6 @@
 =head1 NAME
 
-memcached_behavior_get memcached_behavior_set
+memcached_behavior_get, memcached_behavior_set - Manipulate behavior
 
 =head1 LIBRARY
 
@@ -180,19 +180,28 @@ data, but the send will block because the input buffer in the kernel is full).
 
 =item MEMCACHED_BEHAVIOR_IO_KEY_PREFETCH
 
-The binary protocol works a bit different than the textual protocol in the
-way that a multiget is implemented as a pipe of single get-operations that
-is sent to the server in a chunk. If you use large multigets you may improve
-the latency by setting this value so that you send out the first chunk of
-requests when you hit the specified limit, allowing the server to start
-processing the request and send the data back while the rest of the
-requests is created.
+The binary protocol works a bit different than the textual protocol in
+that a multiget is implemented as a pipe of single get-operations which
+are sent to the server in a chunk. If you are using large multigets from
+your application, you may improve the latency of the gets by setting
+this value so you send out the first chunk of requests when you hit the
+specified limit.  It allows the servers to start processing the requests
+to send the data back while the rest of the requests are created and
+sent to the server.
 
 =item MEMCACHED_BEHAVIOR_NOREPLY
 
 Set this value to specify that you really don't care about the result
 from your storage commands (set, add, replace, append, prepend). 
 
+=item MEMCACHED_BEHAVIOR_NUMBER_OF_REPLICAS
+
+If you just want "a poor mans HA", you may specify the numbers of
+replicas libmemcached should store of each item (on different servers).
+This replication does not dedicate certain memcached servers to store the
+replicas in, but instead it will store the replicas together with all of the
+other objects (on the 'n' next servers specified in your server list).
+
 =back
 
 =head1 RETURN