X-Git-Url: https://git.m6w6.name/?a=blobdiff_plain;f=docs%2Fman%2Flibmemcached.3;h=a0538277ed018e1aaee7e7c72d4706239286099b;hb=11621e78bab29c7535bcdd52c3d8b3f10a150001;hp=433cd52aca9e9352181f49797115719669cd5030;hpb=67456d74f5bd4f354a360d70da503dc58cbe5971;p=m6w6%2Flibmemcached diff --git a/docs/man/libmemcached.3 b/docs/man/libmemcached.3 index 433cd52a..a0538277 100644 --- a/docs/man/libmemcached.3 +++ b/docs/man/libmemcached.3 @@ -1,4 +1,4 @@ -.TH "LIBMEMCACHED" "3" "April 14, 2011" "0.47" "libmemcached" +.TH "LIBMEMCACHED" "3" "July 21, 2011" "0.51" "libmemcached" .SH NAME libmemcached \- Introducing the C Client Library for memcached . @@ -35,6 +35,40 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] #include .sp Compile and link with \-lmemcached + +.sp +.ce +---- + +.ce 0 +.sp +.sp +libMemcached is an open source C/C++ client library and tools for the memcached server (\fI\%http://danga.com/memcached\fP). It has been designed to be light on memory usage, thread safe, and provide full access to server side methods. +.sp +libMemcached was designed to provide the greatest number of options to use Memcached. Some of the features provided: +.INDENT 0.0 +.IP 1. 3 +. +Asynchronous and Synchronous Transport Support. +.IP 2. 3 +. +Consistent Hashing and Distribution. +.IP 3. 3 +. +Tunable Hashing algorithm to match keys. +.IP 4. 3 +. +Access to large object support. +.IP 5. 3 +. +Local replication. +.IP 6. 3 +. +A complete reference guide and documentation to the API. +.IP 7. 3 +. +Tools to Manage your Memcached networks. +.UNINDENT .SH DESCRIPTION .sp "Memcached is a high\-performance, distributed memory object caching @@ -42,23 +76,24 @@ system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load." \fI\%http://danga.com/memcached/\fP .sp \fBlibmemcached\fP is a small, thread\-safe client library for the -memcached protocol. The code has all been written with an eye to allow +memcached protocol. The code has all been written to allow for both web and embedded usage. It handles the work behind routing -particular keys to specific servers that you specify (and values are -matched based on server order as supplied by you). It implements both -a modula and consistent method of object distribution. +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. .sp There are multiple implemented routing and hashing methods. See the -memcached_behavior_set() manpage. +\fBmemcached_behavior_set()\fP manpage for more information. .sp All operations are performed against a \fBmemcached_st\fP 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 \fBmemcached_st\fP. It is not +allocated and then initialized by \fBmemcached_create()\fP. Functions have +been written in order to encapsulate the \fBmemcached_st\fP. It is not recommended that you operate directly against the structure. .sp Nearly all functions return a \fBmemcached_return_t\fP value. -This value can be translated to a printable string with memcached_strerror(3). +This value can be translated to a printable string with +\fBmemcached_strerror()\fP. .sp 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. .sp @@ -78,7 +113,7 @@ PKG_CHECK_MODULES(DEPS, libmemcached >= 0.8.0) AC_SUBST(DEPS_CFLAGS) AC_SUBST(DEPS_LIBS) .sp -Some features of the library must be enabled through memcached_behavior_set(). +Some features of the library must be enabled through \fBmemcached_behavior_set()\fP. .sp Hope you enjoy it! .SH CONSTANTS @@ -129,11 +164,10 @@ Hex value of the version number. "0x00048000" This can be used for comparing ver .UNINDENT .SH THREADS AND PROCESSES .sp -When using threads or forked processes it is important to keep an instance -of \fBmemcached_st\fP per process or thread. Without creating your own locking -structures you can not share a single \fBmemcached_st\fP. You can though call -memcached_quit(3) on a \fBmemcached_st\fP and then use the resulting cloned -structure. +When using threads or forked processes it is important to keep one instance +of \fBmemcached_st\fP per process or thread. Without creating your own +locking structures you can not share a single \fBmemcached_st\fP. However, +you can call \fBmemcached_quit()\fP on a \fBmemcached_st\fP and then use the resulting cloned structure. .SH HOME .sp To find out more information please check: