Closed GoogleCodeExporter closed 9 years ago
It is likely that cache expiration is enforced on get() rather than when you
enumerate the contents, so you are seeing a quirk of the internal
implementation of memcache expiration. You will almost certainly see this same
behavior using MemcacheService directly - and if so, you might want to raise
the issue with Google.
I added a test case to prove that cache expires (see
CachingTests.cacheExpirationWorks()) and it passes, so I feel pretty confident
that Objectify is doing the right thing. I'm guessing the problem is with the
memcache viewer, not with actual expiration.
Original comment by lhori...@gmail.com
on 19 Oct 2013 at 6:57
Original issue reported on code.google.com by
j...@formigas.de
on 14 Aug 2013 at 8:38