Home
last modified time | relevance | path

Searched refs:protocol (Results 1 – 13 of 13) sorted by relevance

/memcached-1.6.32/t/
Dudp.t89 if ($protocol == ::IS_ASCII) {
91 } elsif ($protocol == ::IS_BINARY) {
103 if ($protocol == ::IS_ASCII) {
105 } elsif ($protocol == ::IS_BINARY) {
118 if ($protocol == ::IS_ASCII) {
128 if ($protocol == ::IS_ASCII) {
147 my ($protocol, $req_id, $key) = @_;
151 if ($protocol == ::IS_ASCII) {
161 if ($protocol == ::IS_ASCII) {
185 if ($protocol == ::IS_ASCII) {
[all …]
/memcached-1.6.32/doc/
DMakefile.am3 SPECIFICATIONS = protocol-binary.txt protocol-binary-range.txt
Dprotocol-binary-range.txt16 This memo explains extensions to the memcache binary protocol for use
91 usage patterns, the stateless [UDP] protocol better suits their
93 the memcache protocol [MEMCACHE] in a UDP environment.
149 single UDP packet (noting that the protocol header must also be
Dprotocol-binary.txt17 This memo explains the memcache binary protocol for informational
238 0x80 Request packet for this protocol version
239 0x81 Response packet for this protocol version
241 Magic byte / version. For each version of the protocol, we'll use a
242 different request/response value pair. This is useful for protocol
250 format. As reserved bytes are given defined meaning, the protocol
1195 textual protocol for the full description on how to specify the
Dtls.txt45 holds certificates, a private key, and options regarding the TLS protocol and algorithms.
Dprotocol.txt6 protocol.") A given running memcached server listens on some
21 There are two kinds of data sent in the memcache protocol: text lines
84 Meta commands incorporate most features available in the binary protocol, as
93 These work mixed with normal protocol commands on the same connection. All
169 doesn't conform to the protocol in some way. <error> is a
1244 detailed TLS protocol errors.
1274 of the protocol, and are subject to change for the convenience of
1779 | | | seen a fatal TLS protocol error|
1874 UDP protocol
1885 same format as the TCP protocol described above. In the current
[all …]
/memcached-1.6.32/
Dmemcached.c677 c->protocol = bproto; in conn_new()
721 sfd, c->protocol); in conn_new()
766 switch (c->protocol) { in conn_new()
1302 if (c->protocol == binary_prot) { in out_of_memory()
1448 assert(c->protocol == ascii_prot in complete_nread()
1452 assert(c->protocol == ascii_prot in complete_nread()
1455 if (c->protocol == ascii_prot) { in complete_nread()
2385 c->protocol = binary_prot;
2389 c->protocol = ascii_prot;
2407 c->protocol = binary_prot;
[all …]
Dmemcached.h235 enum protocol { enum
472 enum protocol binding_protocol;
877 enum protocol protocol; /* which protocol this connection speaks */ member
962 …k_transport transport, struct event_base *base, void *ssl, uint64_t conntag, enum protocol bproto);
993 enum network_transport transport, void *ssl, uint64_t conntag, enum protocol bproto);
DLICENSE.itoa_ljust11 https://developers.google.com/protocol-buffers/
DChangeLog279 * Add clarification of flush_all in the protocol docs
444 memcached protocol in the "flush_all" command that allows you to
585 * added doc/protocol.txt
Dthread.c52 enum protocol bproto;
774 uint64_t conntag, enum protocol bproto) { in dispatch_conn_new()
Dstorage.c189 if (c->protocol == binary_prot) { in _storage_get_item_cb()
337 int iovtotal = (c->protocol == binary_prot) ? it->nbytes - 2 : it->nbytes; in storage_get_item()
/memcached-1.6.32/vendor/mcmc/
DREADME.md45 * Does not support the binary protocol, which has been deprecated as of 1.6.0.