[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 Rubinsky <mrubinsk at horde.org>
  Summary            | Use memcache instead of distributed hashtable in
                     | $conf[cache][driver]
  Queue              | Components
  Type               | Enhancement
-State              | New
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-03-30 00:36) 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.

None of the other cache drivers require this to be set in order for  
get()'s lifetime parameter to work, and as far as I know it was like  
this since forever. We use it this way in far more than just  
Horde_Service_Weather. If changes to hashtable *require* this  
parameter to be set in this way, it's a bc break and must be worked  
around in hashtable code.