[Tickets #13085] Re: Use memcache instead of distributed hashtable in $conf[cache][driver]

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13085
------------------------------------------------------------------------------
  Ticket             | 13085
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Use memcache instead of distributed hashtable in
                     | $conf[cache][driver]
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-03-30 16:51) wrote:

> The API documentation for Horde_Cache#set states that $lifetime is  
> the time after which the data becomes *available* for GC, not  
> necessarily the time at which the data is actually invalid. GC !=  
> data invalidity.

Correct.

But note that this value is different than the $lifetime value of  
get(), which is used to explicitly enforce a lifetime value (even if  
it exists in the backend).  So if the weather code needs to expire its  
data after a certain period of time, it needs to use get(), not set().

In other words:
   - set() is used to control cache storage space
   - get() is used to control whether the data itself is valid