Tickets :: Comment on [#13085] Use memcache instead of distributed hashtable in $conf[cache][driver]

* Your Email Address
* Spam protection	Enter the letters below: .__ . .. .. ..__ [__)\| \|\|\/\|\|\/\|[__) [__)\|/\\|\| \|\| \|[__)
Comment	>> 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.
Attachment
Watch this ticket