Lines Matching refs:to
38 time. It is inappropriate to use Internet-Drafts as reference
39 material or to cite them other than as "work in progress."
48 This document is subject to BCP 78 and the IETF Trust's Legal
49 Provisions Relating to IETF Documents
61 to this document. Code Components extracted from this document must
120 Memcache was originally written to make LiveJournal [LJ] faster. It
127 document are to be interpreted as described in [KEYWORDS].
231 Opaque Will be copied back to you in the response.
243 analyzers to distinguish the nature of the packet from the direction
244 which it is moving. Note, it is common to run a memcached instance
248 The version should hopefully correspond only to different meanings of
253 Traffic analysis tools are encouraged to identify memcache packets
255 and otherwise to provide a generic breakdown of the packet. Note,
346 server will respond to each request with zero or multiple packets for
477 You're not guaranteed a response to a getq/getkq cache hit until you
479 bundles up IOs to send to the client in one go.
484 guaranteed to get a response, and you know when the server's done.
699 MUST only succeed if the item exists and has a CAS value identical to
710 errors should not be allowed to go unnoticed.
907 o 8 byte value to add / subtract
917 0| Amount to add |
927 These commands will either add or remove the specified amount to the
935 seeding the value for this key with the provided initial value to
937 to zero.
1125 Close the connection to the server.
1195 textual protocol for the full description on how to specify the
1449 These commands will either append or prepend the specified value to
1463 The following example appends '!' to the 'Hello' key.
1608 packet (no key / no value) to terminate the sequence. Each of the
1691 Bradner, S., "Key words for use in RFCs to Indicate
1698 Thanks to Brad Fitzpatrick, Anatoly Vorobey, Steven Grimm, and Dustin
1701 Thanks to Sean Chittenden, Jonathan Steinert, Brian Aker, Evan