Lines Matching refs:value
84 the server. In all such cases, the actual value sent may either be
86 value), or a number of seconds starting from current time. In the
89 that, the server will consider it to be real Unix time value rather
168 server time). If a negative value is given the item is immediately
175 - <cas unique> is a unique 64-bit value of an existing entry.
176 Clients should use the value returned from the "gets" command
233 - <flags> is the flags value set by the storage command
280 the current data value does not conform to such a representation, the
282 bogus value as if it were 0, leading to confusion). Also, the item
284 that a non-existent key exists with value 0; instead, they will fail.
288 incr <key> <value> [noreply]\r\n
292 decr <key> <value> [noreply]\r\n
296 - <value> is the amount by which the client wants to increase/decrease
305 - "NOT_FOUND\r\n" to indicate the item with this value was not found
307 - <value>\r\n , where <value> is the new value of the item's data,
311 to decrease the value below 0, the new value will be 0. Overflow in
433 A value of "0" disables the sleep, "1000000" (one second) is the max.
489 The response format is in "key=value key2=value2" format, for easy parsing.
495 The value of keys (and potentially other things) are "URI encoded". Since most
539 STAT <name> <value>\r\n
546 <value> is the data. The following is the list of all names sent in
547 response to the "stats" command, together with the type of the value
548 sent for this name, and the meaning of the value.
601 | | | found, but the CAS value did not match. |
702 | chunk_size | 32 | Minimum space allocated for key+value+flags. |
746 STAT items:<slabclass>:<stat> <value>\r\n
868 STAT <slabclass>:<stat> <value>\r\n
869 STAT <stat> <value>\r\n
892 | | value due to a bad CAS id. |
916 STAT <file descriptor>:<stat> <value>\r\n
940 The value of the "state" stat may be one of the following:
1049 monotonically increasing value starting from a random seed, but the client