Well, I'm not sure either, but some googling brough up a buncha msdn2 / asp related things.... I sorta glanced and it seems like a FIFO idea, more or less, which brings up a question I have, although I have no idea if the original poster was wondering this but um
time_t(0) when setting an object in the cache ....time passes....more objects get set....some time_t(0) some time_t(n)... set-new-object time_t(0 or n) ... but cache is full... does it reject the new object or throw out the oldest time_t(0) object? or throw out the oldest time_t(n) object where n>0 but n-has-expired? if i wanted a pure FIFO cache, just set all expiration to NULL? On Fri, Apr 18, 2008 at 8:24 AM, Brian Moon <[EMAIL PROTECTED]> wrote: > Can you explain? I am not sure what you mean by sliding. > > Brian Moon > > > > On Apr 18, 2008, at 1:56 AM, "Simone Busoli" <[EMAIL PROTECTED]> > wrote: > > > > Hello, I have a question about the expiration policy employed by > Memcached. Does it support sliding expiration out of the box or does it have > to be managed at the application level? > > >
