Is this related to this bug? http://code.google.com/p/googleappengine/issues/detail?id=1284
What happens if you create a new instance of the Cache? If you're worried about cost, this should be extremely cheap, as this really only creates a short-lived client instance. On Wed, Mar 24, 2010 at 4:42 AM, moissinac <[email protected]> wrote: > > No one can help about expiration delay of the cache? > > On 19 mar, 16:51, moissinac <[email protected]> wrote: >> By replacing the line >> >> > cache.put(key, foo, exp, MemcacheService.SetPolicy.SET_ALWAYS); >> by >> > cache.put(key, foo); >> >> Thecacheworks, but I loose the 'expirationdelay' functionality >> which I need > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine http://googleappengine.blogspot.com | http://twitter.com/app_engine -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
