[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              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2014-03-31 14:46) wrote:

> No, this is how every Horde_Cache_Storage_* driver is defined.  
> Client code uses Horde_Cache, which delegates the storage to the  
> configured storage driver. Horde_Cache::set() defaults to $lifetime  
> == null, which if you read the code you can see will lead to the  
> storage driver being sent the configured default value for $lifetime.

Ah, I stand corrected. You're right (of course).

But in that case it is still a waste of cache, to keep entries around  
for the configured default value for the cache lifetime, while we  
already know it will not be used anymore after $lifetime seconds in  
the future. We already know that at the time of setting the cache  
value, so it seems a waste not to use that knowledge.