X-Git-Url: https://git.m6w6.name/?a=blobdiff_plain;f=docs%2Fmemcached_get.pod;h=f2f2033c33f0e9018af348c89c49d07ea08c6611;hb=09ee2606fece278264ef65660e12c606f5936347;hp=111a3b614d381234ea0527aefb4da701d7222433;hpb=f9e6b77431a796dd1937f9f49198225a392d95ca;p=awesomized%2Flibmemcached

diff --git a/docs/memcached_get.pod b/docs/memcached_get.pod
index 111a3b61..f2f2033c 100755
--- a/docs/memcached_get.pod
+++ b/docs/memcached_get.pod
@@ -44,6 +44,12 @@ C Client Library for memcached (libmemcached, -lmemcached)
                          size_t *value_length,
                          uint16_t *flags, 
                          memcached_return *error);
+  memcached_return 
+  memcached_fetch_execute(memcached_st *ptr, 
+                          unsigned int (*callback[])(memcached_st *ptr, memcached_result_st *result, void *context),
+                          void *context,
+                          unsigned int number_of_callbacks
+                         )
 
 =head1 DESCRIPTION
 
@@ -80,6 +86,14 @@ to the server. For more information please refer to the memcached_result_st(3)
 help. This function will dynamically allocate a result structure for you
 if you do not pass one to the function.
 
+memcached_fetch_execute() is a callback function for result sets. Instead
+of returning the results to you for processing, it passes each of the
+result sets to the list of functions you provide. It passes to the function
+a memcached_st that can be cloned for use in called the cluster (it can not 
+be used directly). It also passed a result set which does not need to be freed.
+Finally it passes a "context". This is just a pointer to a memory reference
+you supply the calling function. 
+
 memcached_get_by_key() and memcached_mget_by_key() behave in a similar nature
 as memcached_get() and memcached_mget(). The difference is that they take
 a master key that is used for determining which server an object was stored