refreshing the cache time of a key

Oleksandr V. Typlyns'kyi astral at
Thu Feb 28 00:12:34 UTC 2008

Yesterday Feb 27, 2008 at 15:09 Dustin Sallings wrote:

> On Feb 27, 2008, at 13:55, Oleksandr V. Typlyns'kyi wrote:
> >  And I think people use this behavior, but via set after get ;)
> >  With "touch" we can save time and newtwork bandwidth.
> 	Well, more complexity, though.  I suppose it depends on how often 
> people have sessions that don't change, and whether it's worth avoiding 
> the set in favor of a touch after a request.  The get would happen 
> anyway, right?

  The get would happen almost all for session. If user just surf from page 
  to page and don't change profile we can update onli expiration time. In 
  more complex session structures we can use more then one key for each user.
  Another case - chain of cache keys. Than we cen get only few items and 
  touch all other.

KP Media / bigmir)net

More information about the memcached mailing list