Carsten Ziegeler wrote: > > >>-----Original Message----- >>From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] >>Sent: Thursday, September 12, 2002 2:31 PM >>To: [EMAIL PROTECTED] >>Cc: Gerhard Froehlich >>Subject: Re: Big problems with JispFilesystemStore >> >> >>Carsten Ziegeler wrote: >> >> >> >>>Hi, >>> >>>the JispFilesystemStore has some serious problems/bugs - it does >>>not implement the free() or the keys() method! - So if you use >>>this store for caching (and it's the default) your cache >>>might grow and grow - because the store janitor cannot free it!!! >>>
See below... >>>So, I recommend not to use the JispFilesystemStore in it's current >>>state. >>> >>> >>> >>And we can not use FileSystemStore too, I guess you know this... >> >> >> >> >>>I looked at the Jisp API but didn't see a way to get all keys out >>>of the store. Is this right? Does anyone know a way, so we can >>>fix these problems? >>> >>> >>> >>According to http://www.coyotegulch.com/algorithm/jisp/, JISP 2.0 was >>released, which might have necessary methods. >> >> >> >Hopefully! > > > >>IIRC, Gerhard desired working on integrating new JISP version into Cocoon. >> >>PS Why do you need keys()? I've seen your CVS comment... >> >> >> > >The cache validation of the portal invalidates (deletes) all obsolete >profiles >if a base profile has changed. Without getting the keys() this is not >possible. > ... And with keys() it will be awfully slow :-/ In good old days of Filesystem store it could take minutes to "ls" a cache directory.... >And the keys() method is necessary for the store janitor to remove (free()). > No, keys() is not used there. So Janitor is Ok. Same for pipeline - it uses remove(), not keys(). >Or this is only used for memory freeing? > Yes, only memory. Pipeline removes entry from caches when it becomes invalid. Vadim >Carsten > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]