X-Git-Url: https://git.m6w6.name/?a=blobdiff_plain;f=docs%2Flibmemcached.pod;h=b950a63d82cf2f827de4fd4b499366dc85a8243d;hb=c5748c5a1d474145afcf82bd2dfcbfde4a18bd64;hp=1e63c8ce178f345ff4467b9209858a4f2af5ca61;hpb=3b706525e1b66b907905bb9eddd7fd824e8311de;p=awesomized%2Flibmemcached diff --git a/docs/libmemcached.pod b/docs/libmemcached.pod index 1e63c8ce..b950a63d 100755 --- a/docs/libmemcached.pod +++ b/docs/libmemcached.pod @@ -33,7 +33,7 @@ written in order to encapsulate the C. It is not recommended that you operate directly against the structure. Nearly all functions return a C value. -This value can be translated to a printable string with memcached_strerr(3). +This value can be translated to a printable string with memcached_strerror(3). Partitioning based on keys is supported in the library. Using the key partioning functions it is possible to group sets of object onto servers. @@ -106,8 +106,8 @@ Major version value. Such as 1.23.4, would be 4 When using threads or forked processes it is important to keep an instance of C per process or thread. Without creating your own locking -structures you can no share a single C. You can though call -memcached_close(3) on a C and then use the resulting cloned +structures you can not share a single C. You can though call +memcached_quit(3) on a C and then use the resulting cloned structure. =head1 HOME