That's fine for simple date-based cache. If memcached only
supported the "add" and "get" operations, that would be perfectly
sufficient.
I'm talking about covering cases involving set, replace, delete,
flush, incr, cas, append, and other mutation commands.
In these cases, the cache invalidates because something performed
an action that caused the cache to invalidate before it's expiration
date. An L2 cache would need to know this.
--
Dustin Sallings (mobile)
On Dec 8, 2007, at 22:54, dormando <[EMAIL PROTECTED]> wrote:
Having the expiry time returned explicitly instead of part of the
data
does make things slightly easier, but otherwise isn't much of an
advantage.
Timo
I was advocating that point actually ;) What I'm curious about was
Dustin's idea of having a stream of expiration data that a service
could
subscribe to.
-Dormando
