Lines Matching refs:response
59 that the client expects one line of response, which will indicate
66 the client one response line with information about the item, and one
68 finished with the "END" response line.
72 command) either one line of response, or several lines of response
115 behavior of the command. If a flag requests a response flag (ie 't' for TTL
124 seconds of TTL remaining, would return 't20' in the response.
304 to indicate the end of response.
343 The response line to this command can be one of:
383 The response will be one of:
418 The response line to this command can be one of:
444 to indicate the end of response.
472 - if <flag> is 'b', then <key> is a base64 encoded binary value. the response
475 The response looks like:
511 If a response line appearing in a retrieval request is not sent back
530 If the request did not ask for a value in the response (v) flag, the server
531 response looks like:
535 If the request resulted in a miss, the response looks like:
549 - O(token): opaque value, consumes a token and copies back with response
562 These extra flags can be added to the response:
575 If 'b' flag is sent in the response, and a key is returned via 'k', this
585 - O(token): opaque value, consumes a token and copies back with response
590 response belongs to which without also retrieving the key. If the key is very
602 available the "VA" line is normally not sent, and the response is terminated by
619 The data block for a metaget response is optional, requiring this flag to be
620 passed in. The response code also changes from "HD" to "VA <size>"
635 created a 'W' flag is added to the response to indicate to a client that they
657 These extra flags can be added to the response:
680 When combined with the X flag, or the client N or R flags, this extra response
736 - O(token): opaque value, consumes a token and copies back with response
764 - O(token): opaque value, consumes a token and copies back with response
771 the client for normal responses. In the case of metaset, a response that
810 The response is in the format:
854 response lines with the code "DE". It will still return any other responses.
883 The response is in the format:
899 If the 'v' flag is supplied, the response is formatted as:
914 - O(token): opaque value, consumes a token and copies back with response
958 The meta no-op command exists solely to return a static response code. It
963 This returns the static response:
968 For example, with 'mg' the response lines are blank on miss when the 'q' flag
991 The response line could be one of:
1024 The response should always be "OK\r\n"
1065 The response line could be one of:
1087 The response line could be one of:
1099 The response line could be one of:
1111 The response line could be one of:
1127 The response line could be one of:
1155 The response line could be one of:
1178 The response line could be one of:
1210 The response line could be one of:
1216 The response format is in "key=value key2=value2" format, for easy parsing.
1292 response to the "stats" command, together with the type of the value
1325 | response_obj_count | 64u | Total response objects in use |
1749 | conn_mwrite | Writing a complex response, e.g., to a "get" command. |
1761 | conn_write | Writing a simple response (anything that doesn't involve |
1762 | | sending back multiple lines of response data). |
1797 succeeds, and the server sends "OK\r\n" in response (unless "noreply"
1801 response to a retrieval command (unless it's stored again under the
1840 In response, the server sends
1846 and the server sends "OK\r\n" in response (unless "noreply" is given
1882 incomplete response can simply be treated as a cache miss.
1902 is free to use whatever request IDs it likes. The server's response will
1911 datagrams for a given response in sequence number order; the resulting byte
1912 stream will contain a complete response in the same format as the TCP