> -----Original Message-----
> From: Enke, Michael [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 12, 2002 10:51 AM
> To: [EMAIL PROTECTED]
> 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!!!
> > So, I recommend not to use the JispFilesystemStore in it's current
> > state.
> > 
> > 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?
> 
> 
> The first think what I did was to use the
> FilesystemStore. But this throws an exception. See:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12034
> Over the last weeks I submitted several Bugreports with
> solution (not related to JispFilesystemStore)
> but no committer seems to be interested in fixing errors :-(
> 
Yeah, the same old problem...

Ok, unfortunately even if the FilesystemStore would work it has many
more problems/bugs: keys are compared by a simple toString() call,
the generated file names are way too long etc.
So, the only real solution is to either fix the Jisp store or
to rewrite the FilesystemStore.

I will have a look at the bug above.

Thanks
Carsten

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to