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
224 to indicate the end of response.
263 The response line to this command can be one of:
303 The response will be one of:
338 The response line to this command can be one of:
362 The response line could be one of:
395 The response should always be "OK\r\n"
423 The response line could be one of:
435 The response line could be one of:
447 The response line could be one of:
463 The response line could be one of:
483 The response line could be one of:
489 The response format is in "key=value key2=value2" format, for easy parsing.
547 response to the "stats" command, together with the type of the value
947 | conn_mwrite    | Writing a complex response, e.g., to a "get" command.     |
959 | conn_write     | Writing a simple response (anything that doesn't involve  |
960 |                | sending back multiple lines of response data).            |
969 succeeds, and the server sends "OK\r\n" in response (unless "noreply"
973 response to a retrieval command (unless it's stored again under the
1003 In response, the server sends
1009 and the server sends "OK\r\n" in response (unless "noreply" is given
1030 incomplete response can simply be treated as a cache miss.
1050 is free to use whatever request IDs it likes. The server's response will
1059 datagrams for a given response in sequence number order; the resulting byte
1060 stream will contain a complete response in the same format as the TCP