[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:03) wrote:

> It depends. Only when a lifetime value of '0' is passed does this  
> mean that it is never marked for GC. If it is omitted (therefore  
> passing a null), it is marked for GC based on the configured default  
> GC lifetime.

It is probably due to my limited command of the PHP language, but I  
assumed that the below function would set $lifetime to '0' if the  
parameter is not passed (similar to C++):

     public function set($key, $data, $lifetime = 0)
     {
         $key = $this->_params['prefix'] . $key;

         if ($this->_memcache->set($key . '_e', time(), $lifetime) !== false) {
             $this->_memcache->set($key, $data, $lifetime);
         }
     }

Apparently I am wrong here, but in that case I wonder why it would be  
needed to set a default at all.