git.m6w6.name Git - m6w6/libmemcached/blob - docs/memcached_cas.rst

   1 ====================================================
   2 Working with data on the server in an atomic fashion
   3 ====================================================
   4
   5 .. index:: object: memcached_st
   6
   7
   8 --------
   9 SYNOPSIS
  10 --------
  11
  12
  13 #include <libmemcached/memcached.h>
  14
  15 .. c:function:: memcached_return_t memcached_cas(memcached_st *ptr, const char *key, size_t key_length, const char *value, size_t value_length, time_t expiration, uint32_t flags, uint64_t cas);
  16
  17 .. c:function:: memcached_return_t memcached_cas_by_key(memcached_st *ptr, const char *group_key, size_t group_key_length, const char *key, size_t key_length, const char *value, size_t value_length, time_t expiration, uint32_t flags, uint64_t cas);
  18
  19 Compile and link with -lmemcached
  20
  21
  22 -----------
  23 DESCRIPTION
  24 -----------
  25
  26 :c:func:`memcached_cas()` overwrites data in the server as long as the "cas"
  27 value is still the same in the server. You can get the cas value of a result
  28 by calling :c:func:`memcached_result_cas()` on a memcached_result_st(3)
  29 structure. At the point that this note was written cas is still buggy in memached. Turning on tests for it in libmemcached(3) is optional. Please see
  30 :c:func:`memcached_set()` for information on how to do this.
  31
  32 :c:func:`memcached_cas_by_key()` method behaves in a similar method as the non
  33 key methods. The difference is that it uses the :c:type:`group_key` parameter
  34 to map objects to particular servers.
  35
  36 :c:func:`memcached_cas()` is testsed with the :c:type:`MEMCACHED_BEHAVIOR_USE_UDP` behavior enabled. However, when using these operations with this behavior
  37 on, there are limits to the size of the payload being sent to the server.  The
  38 reason for these limits is that the Memcached Server does not allow
  39 multi-datagram requests and the current server implementation sets a datagram
  40 size to 1400 bytes. Due to protocol overhead, the actual limit of the user
  41 supplied data is less than 1400 bytes and depends on the protocol in use as,
  42 well as the operation being executed. When running with the binary protocol,
  43 :c:type:`MEMCACHED_BEHAVIOR_BINARY_PROTOCOL`, the size of the key,value,
  44 flags and expiry combined may not exceed 1368 bytes. When running with the
  45 ASCII protocol, the exact limit fluctuates depending on which function is
  46 being executed and whether the function is a cas operation or not. For
  47 non-cas ASCII set operations, there are at least 1335 bytes available to
  48 split among the key, key_prefix, and value; for cas ASCII operations there
  49 are at least 1318 bytes available to split among the key, key_prefix and value. If the total size of the command, including overhead, exceeds 1400 bytes, a :c:type:`MEMCACHED_WRITE_FAILURE` will be returned.
  50
  51
  52 ------
  53 RETURN
  54 ------
  55
  56
  57 All methods return a value of type :c:type:`memcached_return_t`.
  58 On success the value will be :c:type:`MEMCACHED_SUCCESS`.
  59 Use :c:func:`memcached_strerror()` to translate this value to a printable
  60 string.
  61
  62
  63 ----
  64 HOME
  65 ----
  66
  67
  68 To find out more information please check:
  69 `http://libmemcached.org/ <http://libmemcached.org/>`_
  70
  71
  72 --------
  73 SEE ALSO
  74 --------
  75
  76
  77 :manpage:`memcached(1)` :manpage:`libmemached(3)` :manpage:`memcached_strerror(3)` :manpage:`memcached_set(3)` :manpage:`memcached_append(3)` :manpage:`memcached_add(3)` :manpage:`memcached_prepend(3)` :manpage:`memcached_replace(3)`
  78