libmemcached
libmemcachedutil
libhashkit
Client Applications
Copyright
+ @@ -230,26 +196,24 @@ Memcached. Some of the features provided:âMemcached is a high-performance, distributed memory object caching -system, generic in nature, but intended for use in speeding up dynamic web -applications by alleviating database load.â -http://memcached.org/
-libmemcached is a small, thread-safe client library for the
-memcached protocol. The code has all been written to allow
-for both web and embedded usage. It handles the work behind routing
-individual keys to specific servers specified by the developer (and values are
-matched based on server order as supplied by the user). It implements
-a modular and consistent method of object distribution.
âMemcached is a high-performance, distributed memory object caching system, +generic in nature, but intended for use in speeding up dynamic web applications +by alleviating database load.â http://memcached.org/
+libmemcached is a small, thread-safe client library for the memcached
+protocol. The code has all been written to allow for both web and embedded
+usage. It handles the work behind routing individual keys to specific servers
+specified by the developer (and values are matched based on server order as
+supplied by the user). It implements a modular and consistent method of object
+distribution.
There are multiple implemented routing and hashing methods. See the
-memcached_behavior_set() manpage for more information.
All operations are performed against a memcached_st structure.
-These structures can either be dynamically allocated or statically
-allocated and then initialized by memcached_create(). Functions have
-been written in order to encapsulate the memcached_st. It is not
-recommended that you operate directly against the structure.
Nearly all functions return a memcached_return_t value.
-This value can be translated to a printable string with
-memcached_strerror.
memcached_behavior_set() manpage for more information.
+All operations are performed against a memcached_st structure. These
+structures can either be dynamically allocated or statically allocated and then
+initialized by memcached_create(). Functions have been written in order to
+encapsulate the memcached_st. It is not recommended that you operate directly
+against the structure.
Nearly all functions return a memcached_return_t value. This value can be
+translated to a printable string with memcached_strerror().
Objects are stored on servers by hashing keys. The hash value maps the key to a particular server. All clients understand how this hashing works, so it is possibly to reliably both push data to a server and retrieve data from a server.
@@ -258,20 +222,14 @@ possibly to reliably both push data to a server and retrieve data from a server. applications can use the same memcached servers.Some features of the library must be enabled through memcached_behavior_set().
A number of constants have been provided for in the library.
- -No global variables are used in this library.
-memcached_st structures are thread-safe, but when using threads or
-forked processes it is important to keep one instance of memcached_st
-per process or thread. Without creating your own locking structures you can not
-share a single memcached_st. However, you can call
-memcached_quit() on a memcached_st and then use the resulting
-cloned structure.
memcached_st structures are thread-safe, but when using threads or forked
+processes it is important to keep one instance of memcached_st per process or
+thread. Without creating your own locking structures you can not share a single
+memcached_st. However, you can call memcached_quit() on a memcached_st and
+then use the resulting cloned structure.