X-Git-Url: https://git.m6w6.name/?a=blobdiff_plain;f=docs%2Fmemcached_delete.pod;h=e104eab560a0062c6efece63858b1bb5b55b28af;hb=31ed3cfdb9f1b7cf00a93dfefbe067b468a67507;hp=07ec865ca86cc2672576c5fb3aec23244b9592db;hpb=b4de8d3fd063b9017797dd9809ab3acb8a537606;p=m6w6%2Flibmemcached diff --git a/docs/memcached_delete.pod b/docs/memcached_delete.pod index 07ec865c..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 @@ -44,7 +47,7 @@ means that the message was queued for delivery. =head1 HOME To find out more information please check: -L +L =head1 AUTHOR