diff options
| author | dormando <dormando@rydia.net> | 2021-06-09 15:09:53 -0700 |
|---|---|---|
| committer | dormando <dormando@rydia.net> | 2021-06-10 11:24:15 -0700 |
| commit | 6a1802cb2a180971c328d9820df23336eec72c0f (patch) | |
| tree | b90933420ae79f7e6e95389bdf503f4c73c8c738 /doc | |
| parent | 3d178cfd3241764acb789c166f1b0209457f2aff (diff) | |
| download | memcached-6a1802cb2a180971c328d9820df23336eec72c0f.tar.gz | |
meta: response code OK -> HD
I had the response code as "HD" in the past, but standardized on OK
while merging a number of "OK-like" rescodes together. This was a
mistake; as many "generic" memcached response codes use "OK". Most of
these are management or specialized uncommon commands.
With this, a client response parser can know for sure if a response is
to a meta command, or some other command.
`-o meta_response_old` starttime option has been added, valid for the
next 3 months, which switches the response code back from HD to OK. In
case any existing users depended on this and need time to migrate.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/protocol.txt | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/protocol.txt b/doc/protocol.txt index bbaabef..623982d 100644 --- a/doc/protocol.txt +++ b/doc/protocol.txt @@ -523,7 +523,7 @@ VA <size> <flags>*\r\n If the request did not ask for a value in the response (v) flag, the server response looks like: -OK <flags>*\r\n +HD <flags>*\r\n If the request resulted in a miss, the response looks like: @@ -609,7 +609,7 @@ access time. - v: return item value in <data block> The data block for a metaget response is optional, requiring this flag to be -passed in. The response code also changes from "OK" to "VA <size>" +passed in. The response code also changes from "HD" to "VA <size>" These flags can modify the item: - N(token): vivify on miss, takes TTL as a argument @@ -698,7 +698,7 @@ the reply, which is of the format: Where CD is one of: -- "OK" (STORED), to indicate success. +- "HD" (STORED), to indicate success. - "NS" (NOT_STORED), to indicate the data was not stored, but not because of an error. @@ -746,7 +746,7 @@ See description under 'Meta Get' Noreply is a method of reducing the amount of data sent back by memcached to the client for normal responses. In the case of metaset, a response that -would start with "OK" will not be sent. Any other code, such as "EX" +would start with "HD" will not be sent. Any other code, such as "EX" (EXISTS) will still be returned. Errors are always returned. @@ -782,7 +782,7 @@ The response is in the format: Where CD is one of: -- "OK" (DELETED), to indicate success +- "HD" (DELETED), to indicate success - "NF" (NOT_FOUND), to indicate that the item with this key was not found. @@ -847,7 +847,7 @@ The response is in the format: Where CD is one of: -- "OK" to indicate success +- "HD" to indicate success - "NF" (NOT_FOUND), to indicate that the item with this key was not found. |