Lines Matching refs:flags

89 Meta flags are not to be confused with client bitflags, which is an opaque
90 number passed by the client. Meta flags change how the command operates, but
109 Where <RC> is a 2 character return code. The number of flags returned are
110 based off of the flags supplied.
192 set <key> <flags> <exptime> <bytes>\r\n
195 key, flags, and exptime are ignored for authentication. Bytes is the length
209 <command name> <key> <flags> <exptime> <bytes> [noreply]\r\n
210 cas <key> <flags> <exptime> <bytes> <cas unique> [noreply]\r\n
226 The append and prepend commands do not accept flags or exptime.
235 - <flags> is an arbitrary 16-bit unsigned integer (written out in
239 Note that in memcached 1.2.1 and higher, flags may be 32-bits, instead
308 VALUE <key> <flags> <bytes> [<cas unique>]\r\n
313 - <flags> is the flags value set by the storage command
448 VALUE <key> <flags> <bytes> [<cas unique>]\r\n
453 - <flags> is the flags value set by the storage command
498 memcached. Based on the flags supplied, it can replace all of the commands:
501 mg <key> <flags>*\r\n
505 - <flags> are a set of single character codes ended with a space or newline.
506 flags may have token strings after the initial character.
519 VA <size> <flags>*\r\n
524 - <flags>* are flags returned by the server, based on the command flags.
525 They are added in order specified by the flags sent.
533 HD <flags>*\r\n
541 The flags used by the 'mg' command are:
545 - f: return client flags token
556 These flags can modify the item:
562 These extra flags can be added to the response:
567 The flags are now repeated with detailed information where useful:
581 The above two flags return the value of "hit before?" and "last access time"
622 These flags can modify the item:
643 Can be combined with CAS flags to gate the update further.
657 These extra flags can be added to the response:
660 When combined with N or R flags, a client may be informed they have "won"
680 When combined with the X flag, or the client N or R flags, this extra response
689 on the flags supplied, it can replace all storage commands (see token M) as
692 ms <key> <datalen> <flags>*\r\n
698 - <flags> are a set of single character codes ended with a space or newline.
699 flags may have strings after the initial character.
712 <CD> <flags>*\r\n
727 The flags used by the 'ms' command are:
733 - F(token): set client flags to token (32 bit unsigned numeric)
743 The flags are now repeated with detailed information where useful:
756 - F(token): set client flags to token (32 bit unsigned numeric)
758 Sets flags to 0 if not supplied.
803 md <key> <flags>*\r\n
807 - <flags> are a set of single character codes ended with a space or newline.
808 flags may have strings after the initial character.
812 <CD> <flags> <tokens>*\r\n
823 The flags used by the 'md' command are:
835 The flags are now repeated with detailed information where useful:
876 ma <key> <flags>*\r\n
880 - <flags> are a set of single character codes ended with a space or newline.
881 flags may have strings after the initial character.
885 <CD> <flags> <tokens>*\r\n
901 VA <size> <flags>*\r\n
904 The flags used by the 'ma' command are:
921 The flags are now repeated with detailed information where useful:
959 takes no flags, no arguments.
1175 A user may then take each line, append any flags they want, and run those
1480 | chunk_size | 32 | Minimum space allocated for key+value+flags. |
1530 | client_flags_size | 32u | Size in bytes of client flags |