From 1e10c31a1803f16cafe091f6ad0fd991da5609fd Mon Sep 17 00:00:00 2001 From: Peter Schojer Date: Mon, 29 Oct 2007 07:14:12 +0000 Subject: [PATCH] Updated docu for ExpireCache --- Foundation/include/Poco/ExpireCache.h | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/Foundation/include/Poco/ExpireCache.h b/Foundation/include/Poco/ExpireCache.h index 280a1e098..098566e53 100644 --- a/Foundation/include/Poco/ExpireCache.h +++ b/Foundation/include/Poco/ExpireCache.h @@ -1,7 +1,7 @@ // // ExpireCache.h // -// $Id: //poco/Main/Foundation/include/Poco/ExpireCache.h#4 $ +// $Id: //poco/Main/Foundation/include/Poco/ExpireCache.h#5 $ // // Library: Foundation // Package: Cache @@ -49,7 +49,11 @@ namespace Poco { template class ExpireCache: public AbstractCache > - /// An ExpireCache caches entries for a fixed time period (per default 10 minutes) + /// An ExpireCache caches entries for a fixed time period (per default 10 minutes). + /// Entries expire independently of the access pattern, i.e. after a constant time. + /// If you require your objects to expire after they were not accessed for a given time + /// period use a Poco::AccessExpireCache. + /// /// Be careful when using an ExpireCache. A cache is often used /// like cache.has(x) followed by cache.get x). Note that it could happen /// that the "has" call works, then the current execution thread gets descheduled, time passes,