[Tickets #13085] 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
  Created By         | arjen+horde at de-korte.org
  Summary            | Use memcache instead of distributed hashtable in
                     | $conf[cache][driver]
  Queue              | Components
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2014-03-28 11:02) wrote:

The distributed hashtable driver doesn't support the lifetime argument  
and as such is not a very good choice for the $conf[cache][driver]:

     /**
      * NOTE: This driver ignores the lifetime argument.
      */
     public function get($key, $lifetime = 0)
     {
         return $this->_hash->get($this->_params['prefix'] . $key);
     }

This breaks applications that require the cache driver to tell the  
information is expired. For instance,  
Horde/Service/Weather/WeatherUnderground.php will only refresh the  
information if it is expired. This never happens with the distributed  
hashtable, because the lifetime is ignored and once the data is  
retrieved, the same (stale) data will be served indefinitely.

Before the distributed hashtable was introduced, it was possible to  
directly configure memcache as a cache driver (which does support the  
timeout variable). It would be great if this functionality was  
restored here, since some applications seem to depend on the timeout  
to be honored.