[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         | arjen+horde at de-korte.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
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2014-03-30 10:55) 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.

That's true, but would it hurt to set the lifetime? All cache drivers  
will default to a lifetime of '0', which means data will never be GC.  
So if that is not set by Horde_Service_Weather, this is what we'll  
get. That is not what we want either, because this will mean that the  
cache will slowly fill up with entries that are never going to be  
removed.