1. From what I remember, no. The initial expiry time is the set expiration. That being said, accessing a value pushes the key/value pair to the head of the LRU queue, so at the very least, the values won't be LRU expired when more Memcache capacity is required.
2. If I understand you correctly, the operation you're looking for is probably CAS - Memcache check-and-set. Unfortunately, we don't support this operation right now. There are ways to implement similar functionality with INCR/DECR (atomic operations). -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Wed, Dec 8, 2010 at 6:23 PM, Thomas Wiradikusuma <wiradikus...@gmail.com>wrote: > Hi guys, > > Is memcache's expire strategy work like http session's? > > In http session, if you set it to expire in 30 minutes and you access > a page in minute 29th, it will be prolonged for another 30 minutes. > Is this also the case for memcache? If not, is there any "atomic" way > to do it? (i.e. not by doing get-and-put) > > Second question, I have an entry that will be updated by lots of > users, > is there any "get-for-update" for memcache? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
