[dev] Horde_Cache_xcache

Michael Rubinsky mike at theupstairsroom.com
Sun May 13 16:37:47 UTC 2007


I'm trying to troubleshoot some caching issues I'm having. The cache  
seems to work as expected when using the file based cache but behaves  
very oddly when using xcache.

In looking at the xcache code, I don't understand how the *_expire  
entries are being used.  It looks like they are there to persist the  
creation time, since xcache sets the expire time on cache creation,  
but Horde_Cache doesn't take a lifetime during ::set().  OK, that much  
I can understand.  But I don't follow the logic when dealing with the  
the expire times.  When ::exists is called, it just passes it through  
to the native xcache_exists() function - which will always be true  
since it was created with a '0' expire time. But then when trying to  
get the data, ::_setExpire is called - and that seems to unset the  
cache value every time, so by the time xcache_get() is called, the  
cache is gone.

Am I just missing something obvious here or is this broken?

-- 
Thanks,
Mike

"Am I getting old, or has the supermarket been playing great music lately?"



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 2013 bytes
Desc: PGP Public Key
Url : http://lists.horde.org/archives/dev/attachments/20070513/5877feb3/attachment.bin 


More information about the dev mailing list