@@ -225,20 +246,20 @@
server. All methods take a
key, and
key_length to store the object. Keys
are currently limited to 250 characters when using either a version of memcached
which is 1.4 or below, or when using the text protocol. You must supply both a
-value and a length. Optionally you may test an expiration time for the object
-and a 16 byte value (it is meant to be used as a bitmap).
flags is a 4byte
-space that is stored alongside of the main value. Many sub libraries make use of
+value and a length. Optionally you may set an expiration time for the object
+and a 16 bit value (it is meant to be used as a bitmap).
flags is a 4 byte
+space that is stored along the main value. Many sub libraries make use of
this field, so in most cases users should avoid making use of it.
memcached_prepend() places a segment of data before the last piece of data
stored. Currently expiration and key are not used in the server.
memcached_append() places a segment of data at the end of the last piece of data
stored. Currently expiration and key are not used in the server.
memcached_prepend_by_key() and memcached_append_by_key() methods both behave in
-a similar method as the non key methods. The difference is that they use their
+a similar manner as the non key methods. The difference is that they use their
group_key parameter to map objects to particular servers.
If you are looking for performance, memcached_set() with non-blocking IO is the
fastest way to store data on the server.
-
All of the above functions are tested with the MEMCACHED_BEHAVIOR_USE_UDP
+
All of the above functions are tested with the MEMCACHED_BEHAVIOR_USE_UDP
behavior enabled. However, when using these operations with this behavior on,
there are limits to the size of the payload being sent to the server. The
reason for these limits is that the Memcached Server does not allow
@@ -246,7 +267,7 @@ multi-datagram requests and the current server implementation sets a datagram
size to 1400 bytes. Due to protocol overhead, the actual limit of the user
supplied data is less than 1400 bytes and depends on the protocol in use as,
well as the operation being executed. When running with the binary protocol,
-MEMCACHED_BEHAVIOR_BINARY_PROTOCOL, the size of the key,value, flags and
+MEMCACHED_BEHAVIOR_BINARY_PROTOCOL, the size of the key,value, flags and
expiry combined may not exceed 1368 bytes. When running with the ASCII protocol,
the exact limit fluctuates depending on which function is being executed and
whether the function is a cas operation or not. For non-cas ASCII set
@@ -294,11 +315,20 @@ will be
+
+
© Copyright