From: Sebastian K. <seb...@mu...> - 2004-07-21 16:16:23
|
On Tuesday 20 July 2004 10:40, Endre St=F8lsvik wrote: > If the templates were put into the cache using "soft references" .. they are, see WebMacro.defaults: # Advanced properties: ReloadingCacheManager.*.UseSoftReferences: TRUE > | BTW, the thread is started by a class in the concurrent package, another > | _library_... ;) > > Well, another bad library! ;) > > Really, I don't like libraries that fire up Threads w/o me asking in > particular for it. A program with millions of Threads, where each have one > specific stupid little chore. [snip] > And, btw, I do know that the concurrent package is very nice, but firing > up Threads here and there and everywhere is really bad in my opinion, > anywhichway - one immediately get such problems as we now face. to be fair to that library: If you instantiate a ClockDaemon object and=20 provide it with a ThreadFactory, you more or less expect it to start thread= s,=20 don't you? ;) > | However, one could add logic to only start this thread, if the > | functionality to remove templates from the cache after some time is > | actually used (e.g. ExpireTime is set to a positive value). > > YES! YES! YES!!! > > Ehh.. I'd love to see this functionality implemented.. ;) > (As a first step) I just checked this today and found, that this is actually is the behaviour= of=20 2.0b1. Just put this line into your WebMacro.properties and WebMacro won't= =20 fire up any threads, as far as I can see. ReloadingCacheManager.*.ExpireTime: -1 Sebastian =2D-=20 Sebastian Kanthak PGP/GnuPG: http://www.muehlheim.de/~skanthak/pgp.html |