Lines Matching refs:t
26 stream. The server doesn't care about byte order issues in
27 unstructured data and isn't aware of them. There are no limitations on
48 clients wouldn't need to use such long keys); the key must not include
70 All other commands don't involve unstructured data. In all of them,
106 doesn't conform to the protocol in some way. <error> is a
114 serving the client (this shouldn't normally happen), the server will
136 "add" means "store this data, but only if the server *doesn't* already
180 reply. NOTE: if the request line is malformed, the server can't
199 condition for an "add" or a "replace" command wasn't met.
283 must already exist for incr/decr to work; these commands won't pretend
314 Note also that decrementing a number such that it loses length isn't
317 optimization, so you also shouldn't rely on that.
416 TTL's, but aren't accessed very often. This system is not required for normal
665 | | | freelist when it wasn't expecting to. |
832 operation. If you don't want to incur this, leave it off.
929 | | socket types (such as UNIX-domain) don't have |
959 | conn_write | Writing a simple response (anything that doesn't involve |
975 doesn't actually free all the memory taken up by existing items; that
1028 delivery, so should only be used for operations that aren't required to