A friendly client to talk to a Memcached server.
A friendly client to talk to a Memcached server.
The Memcached protocol docs for details on the API.
The result of a check and set command.
The result of a check and set command.
A Client connected to an individual Memcached server.
A Client connected to an individual Memcached server.
Evaluates a given Memcached operation and returns the result.
Map-based mock client for testing
Map-based mock client for testing
this class now respects expiry times. If you want the old expiry-ignoring behavior, use MockClient.ignoresTtl()
PHP memcache-client (memcache.so) compatible client.
Builder for memcache-client (memcache.so) compatible client.
A partitioned client is a client that delegates to an actual client based on the key value.
A partitioned client is a client that delegates to an actual client based on the key value. Subclasses implement clientOf to choose the Client.
This class is designed to support replicated memcached setups.
This class is designed to support replicated memcached setups. It supports a limited subset of operations (just get, set, and delete).
Ruby memcache-client (MemCache) compatible client.
Builder for memcache-client (MemCache) compatible client.
Twemcache commands implementation.
Twemcache commands implementation. This trait can only be mixed into a memcache client implementation as extension.
Twemcache commands implementation for a partitioned client.
Twemcache commands implementation for a partitioned client. This trait can only be mixed into a PartitionedClient that is delegating twemcache compatible clients.
A com.twitter.finagle.Resolver for resolving destination names associated with Twitter cache pools.
Indicates that an error occurred while resolving a cache address.
Indicates that an error occurred while resolving a cache address. See com.twitter.finagle.memcached.TwitterCacheResolver for details.
A zk monitor trait that assists with monitoring a given zk path for any node data change, in which the provided zk data handling implementation will be invoked.
A zk monitor trait that assists with monitoring a given zk path for any node data change, in which the provided zk data handling implementation will be invoked.
This monitor will maintain a queue so that every work item triggered by zk event will be processed in an order with a back off policy. It also set-up a zookeeper connection watcher by default to re-set the data change watcher even during zk re-connect.
The monitor will set-up all watcher properly kick off the loop to process future event; you can also invoke loadZKData() in your class anytime to force reading zk data and apply it.
Example use cases are: - zookeeper based CachePoolCluster uses this to monitor cache pool members change - zookeeper based MigrationClient uses this ot monitor migration state transitioning