[dev] Horde_Cache expiration question

[Duck]

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.

Duck