Lines Matching refs:it
11 just close the connection at any moment it no longer needs it. Note,
25 unstructured data in exactly the same way it received it, as a byte
36 data from a server, it must use the length of the data block (which it
38 the fact that \r\n follows the end of the data block, even though it
46 that are interested in storing and retrieving it. Currently the
65 requested keys; after that for each item the server finds it sends to
116 remaining), it is returned in the same order as they were in the original
149 that, the server will consider it to be real Unix time value rather
176 of severe server errors, which make it impossible to continue
231 only if no one else has updated since I last fetched it."
243 - <exptime> is expiration time. If it's 0, the item never expires
244 (although it may be deleted from the cache to make place for other
245 items). If it's non-zero (either Unix time or offset in seconds from
246 current time), it is guaranteed that clients will not be able to
253 it's followed by an empty data block).
261 parse "noreply" option reliably. In this case it may send the error
262 to the client, and not reading it on the client side will break
282 a "cas" command has been modified since you last fetched it.
358 in-place, incrementing or decrementing it. The data for the item is
362 bogus value as if it were 0, leading to confusion). Also, the item
394 Note also that decrementing a number such that it loses length isn't
403 without fetching it.
498 memcached. Based on the flags supplied, it can replace all of the commands:
513 have the item (because it was never stored, or stored
572 it up. This allows storing and fetching of binary packed keys, so long as they
613 It is possible to access an item without causing it to be "bumped" to the head
625 Normally when an item is created it is given a CAS value from an internal
633 items. If supplied, and metaget does not find the item in cache, it will
649 the right to recache an item. This allows refreshing an item before it leads to
662 notified that it should cache or update an item. Further clients requesting
672 client that an object needs to be updated, and that it should make a decision
675 This is used when you want to convince clients to recache an item, but it's
682 recaching this item. If there is data supplied it may use it, or the client
689 on the flags supplied, it can replace all storage commands (see token M) as
722 CAS semantics has been modified since you last fetched it.
760 - I: invalid. set-to-invalid if CAS is older than it should be.
792 a new item on a miss. If N is supplied, and append reaches a miss, it will
844 it as stale. This means when it is later fetched by metaget, the client will
864 This deletes the value off of an item (by replacing it with an empty value
1002 - "NOTFULL [message]" dest class must be full to move new pages to it
1108 allows you to avoid scanning all of very large slabs when it is unlikely to
1121 head. The crawler cannot be stopped or restarted until it completes the
1124 The special keyword "all" instructs it to crawl all slabs with items in
1143 items by directly walking the hash table instead of the LRU's. This makes it
1169 items by directly walking the hash table instead of the LRU's. This makes it
1208 space-separated. Logs will be sent to the watcher until it disconnects.
1230 This means a "set" command would also emit an item_get log, as it checks for
1231 an item before replacing it. Multigets should also emit multiple lines.
1261 The command "stats" is used to query the server about statistics it
1267 it causes the server to output general-purpose statistics and
1268 settings, documented below. In the other form it has some arguments:
1433 | | | freelist when it wasn't expecting to. |
1567 before it expired.
1569 time set had to be evicted from the LRU before it
1621 lock while it iterates the items. 1.4.27 and greater are safe.
1649 If an error happens, it will return:
1657 it would make the feature too slow to be usable.
1754 | | of parsing it or executing it. |
1759 | | waiting for the rest of it to arrive (note the difference |
1801 response to a retrieval command (unless it's stored again under the
1805 definition of what flush_all does is the following: it causes all
1856 when it no longer needs it, without issuing this command.
1881 succeed; typically it is used for "get" requests where a missing or
1900 The request ID is supplied by the client. Typically it will be a
1902 is free to use whatever request IDs it likes. The server's response will