Comment #1 on issue 372 by [email protected]: no way to get without
bumping LRU, aka "peek"
http://code.google.com/p/memcached/issues/detail?id=372
IMO, you are fixing the wrong problem. In our stack, there is only one
object that reads/writes a cache item. This controls the state of the
cache. Therefore we have no need to fix the cache. Shouldn't you fix that
problem? You are want memcached to allow your application logic to be messy.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
