From 31ed3cfdb9f1b7cf00a93dfefbe067b468a67507 Mon Sep 17 00:00:00 2001 From: Brian Aker Date: Sat, 17 Apr 2010 14:47:32 -0700 Subject: [PATCH] Updating docs. --- docs/memcached_delete.pod | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/docs/memcached_delete.pod b/docs/memcached_delete.pod index 89bff56a..e104eab5 100644 --- a/docs/memcached_delete.pod +++ b/docs/memcached_delete.pod @@ -23,15 +23,18 @@ C Client Library for memcached (libmemcached, -lmemcached) =head1 DESCRIPTION -memcached_delete() is used to delete a particular key. An expiration value -can be applied so that the key is deleted after that many seconds, but this -will only work if you are using a 1.2.x server. If you are using a 1.2.x -server and you want to use the expiration value, please call memcached_version -one time for the memcached_st instance. If you don't do this no-reply and -buffered mode will be disabled to avoid getting out of sync with the server. +memcached_delete() is used to delete a particular key. memcached_delete_by_key() works the same, but it takes a master key to find the given value. +Expiration works by placing the item into a delete queue, which means that +it won't possible to retrieve it by the "get" command, but "add" and +"replace" command with this key will also fail (the "set" command will +succeed, however). After the time passes, the item is finally deleted from server memory. + +Please note the the Danga memcached server removed support for expiration in +the 1.4 version. + =head1 RETURN A value of type C is returned -- 2.30.2