You could just set the memory size to some very small number like 1. This way everything will go right to disk.
> -----Original Message----- > From: Vossberg, Michal [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 04, 2003 6:49 AM > To: '[EMAIL PROTECTED]' > Subject: Spooling after each update > > Hi, > we are implementing an auxiliary disk cache plugin that better suits out > needs. > For this, I want each element explicitly put to disk with the update of > the > memory cache, not only spool them lru after reaching the limit. > I added the spooling to the aux-update part of the CompositeCache update > method > which works fine but I wonder if that's the best (and intended) place. Any > other > idea without intruding the core? > Also, doing this the spooling of the memory manager becomes somewhat > redundant. What's the best way to turn it off but still keep the limit of > the memory cache. > I don't see that setting the element attributes to isSpool=false will help > as it's > not being checked in the spooling method (and in fact it doesn't)!? > Any advice will be greatly appreciated, > Thanks > Michal > > --- Michal Vossberg > Development Mobile Applications > Jamba! AG - Pfuelstrasse 5 - 10997 Berlin > Phone: +49-30-69538-176 > Fax: +49-30-69538-599 > Web: http://www.jamba.de > WAP: http://wap.jamba.de/ > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
