Hi folks, we are just delving a lot further into the use of memcache in our cake app, and we're somewhat perpelxed as to why cake's MemcacheEngine when setting & getting cache vars utilises a second cache entry holding the cache expiry time - when the method Memcache::set has an expires/ttl variable that would take care of this for us? As far as im aware this is also the case for Xcache & APC, where a native expiry type scenario is already handled in the provided methods/functions?
Just wondering if someone might have an inkling of why this is, or maybe one of the core gurus can explain a little further? Cheers, Paul. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
