Lines Matching refs:data
13 than reopen them every time they need to store or retrieve data. This
21 There are two kinds of data sent in the memcache protocol: text lines
22 and unstructured data. Text lines are used for commands from clients
23 and responses from servers. Unstructured data is sent when a client
24 wants to store or retrieve data. The server will transmit back
25 unstructured data in exactly the same way it received it, as a byte
27 unstructured data and isn't aware of them. There are no limitations on
28 characters that may appear in unstructured data; however, the reader
29 of such data (either a client or a server) will always know, from a
30 preceding text line, the exact length of the data block being
33 Text lines are always terminated by \r\n. Unstructured data is _also_
35 may also appear inside the data. Therefore, when a client retrieves
36 data from a server, it must use the length of the data block (which it
37 will be provided with) to determine where the data block ends, and not
38 the fact that \r\n follows the end of the data block, even though it
45 is a text string which should uniquely identify the data for clients
57 "prepend" and "cas") ask the server to store some data identified by a
58 key. The client sends a command line, and then a data block; after
63 retrieve data corresponding to a set of keys (one or more keys in one
67 data block with the item's data; this continues until the server
70 All other commands don't involve unstructured data. In all of them,
122 can return new data or reflect information, in the same order they were
214 "set" means "store this data".
216 "add" means "store this data, but only if the server *doesn't* already
217 hold data for this key".
219 "replace" means "store this data, but only if the server *does*
220 already hold data for this key".
222 "append" means "add this data to an existing key after existing data".
224 "prepend" means "add this data to an existing key before existing data".
227 They update existing data portions, and ignore new flag and exptime
230 "cas" is a check and set operation which means "store this data but
233 - <key> is the key under which the client asks to store the data
236 decimal) that the server stores along with the data and sends back
238 store data-specific information; this field is opaque to the server.
251 - <bytes> is the number of bytes in the data block to follow, *not*
253 it's followed by an empty data block).
265 After this line, the client sends the data block:
267 <data block>\r\n
269 - <data block> is a chunk of arbitrary 8-bit data of length <bytes>
272 After sending the command line and the data block the client awaits
277 - "NOT_STORED\r\n" to indicate the data was not stored, but not
299 which is received as a text line followed by a data block. After all
309 <data block>\r\n
315 - <bytes> is the length of the data block to follow, *not* including
321 - <data block> is the data for this item.
357 Commands "incr" and "decr" are used to change data for some item
358 in-place, incrementing or decrementing it. The data for the item is
360 the current data value does not conform to such a representation, the
387 - <value>\r\n , where <value> is the new value of the item's data,
439 which is received as a text line followed by a data block. After all
449 <data block>\r\n
455 - <bytes> is the length of the data block to follow, *not* including
461 - <data block> is the data for this item.
483 Each of the keys and values are the internal data for the item.
497 The meta get command is the generic command for retrieving key data from
509 text line followed by an optional data block.
520 <data block>\r\n
522 - <size> is the size of <data block> in bytes, minus the \r\n
527 - <data block> is the data for this item. Note that the data block is
554 - v: return item value in <data block>
591 long this can generate a lot of traffic, especially if the data block is very
600 Noreply is a method of reducing the amount of data sent back by memcached to
617 - v: return item value in <data block>
619 The data block for a metaget response is optional, requiring this flag to be
628 external system to version cache data (row versions, clocks, etc).
638 The automatically created item has 0 bytes of data.
663 the item can use the existing data block (if valid or stale), retry, wait, or
673 o if potentially stale data is safe to use.
676 safe to use pre-existing data while the recache happens.
682 recaching this item. If there is data supplied it may use it, or the client
688 The meta set command a generic command for storing data to memcached. Based
696 - <datalen> is the length of the payload data.
701 After this line, the client sends the data block:
703 <data block>\r\n
705 - <data block> is a chunk of arbitrary 8-bit data of length supplied by an 'S'
706 flag and token from the request line. If no 'S' flag is supplied the data
709 After sending the command line and the data block the client awaits
718 - "NS" (NOT_STORED), to indicate the data was not stored, but not
770 Noreply is a method of reducing the amount of data sent back by memcached to
781 A: "append" command. If item exists, append the new value to its data.
782 P: "prepend" command. If item exists, prepend the new value to its data.
793 create a new item seeded with the data from the append command. It uses the
845 be supplied an 'X' flag to show the data is stale and needs to be recached.
1262 maintains and other internal data. It has two forms. Without
1272 Depending on <args>, various internal data is sent by the server. The
1273 kinds of arguments and the data sent are not documented in this version
1291 <value> is the data. The following is the list of all names sent in
1540 item storage per slab class. The data is returned in the format:
1573 recently active your evicted data is.
1623 The data is returned in the following format:
1673 information along with some totals. The data is returned in the format:
1693 | cmd_set | Total number of set requests storing data in this class. |
1714 for new connections. The data is returned in the format:
1751 | conn_nread | Reading extended data, typically for a command such as |
1755 | conn_read | Reading newly-arrived command data. |
1762 | | sending back multiple lines of response data). |
1884 Each UDP datagram contains a simple frame header, followed by data in the