Lines Matching refs:in
17 in a UDP environment.
23 faster when cached data is available in memcache.
27 This Internet-Draft is submitted in full conformance with the
38 material or to cite them other than as "work in progress."
49 (http://trustee.ietf.org/license-info) in effect on the date of
61 include Simplified BSD License text as described in Section 4.e of
63 described in the Simplified BSD License.
88 faster when cached data is available in memcache.
93 the memcache protocol [MEMCACHE] in a UDP environment.
95 It is a goal of this document to provide sufficient information in
103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
104 document are to be interpreted as described in [KEYWORDS].
121 The magic bytes remains the same as in [MEMCACHE].
138 There are no new data types in this extension.
145 described in [MEMCACHE].
156 contained in the Value field of the packet, SHOULD be the maximum
205 key contained in a given packet. A client receives enough
206 information in each Get Range extras to construct an appropriately
207 sized buffer in its own memory and blindly insert the contents of the
251 beyond those discussed in [MEMCACHE].
256 Bradner, S., "Key words for use in RFCs to Indicate
260 Bradner, S., "Key words for use in RFCs to Indicate