[dev] Horde_Cache expiration question

[Chuck Hagenbuch]

Quoting Duck <duck at obala.net>:

> Horde_Cache sets the expiration whenever we deal with a cache entry. But PEAR
> Cache, APC, eAccellerator and memcache set the expiration on the cache
> creation. Are any special reason for a different approach? In this way in the
> most cache implementation we must deal with two entries. One for the cache
> value and one for the TTL. And worst, we have an not needed overhead when a
> cache key is outputted. Since we must check the expiration time when the
> cache is outputted.

I see your point, but we can't change it right now for backwards  
compatibility reasons, unless you can think of something clever that  
I'm not seeing right now. Otherwise we could do this in Horde 4 - you  
can put it on the bc-breaking issues wiki page.

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris