Am 28.07.2014 um 15:14 schrieb Sven Van Caekenberghe <sven@stfx.eu>:
On 28 Jul 2014, at 14:59, Norbert Hartl <norbert@hartl.name> wrote:
Am 28.07.2014 um 14:19 schrieb Sven Van Caekenberghe <sven@stfx.eu>:
Hi Norbert,
Neo-Caching was an experiment, a proof of concept, it has been integrated in Pharo. See category 'System-Caching', the hierarchy AbstractCache, LRUCache and TTLCache.
Ah, good to know, thanks. That's even better because it seems to be in pharo3.
Regarding the TTLCache: If I want obsolete keys to vanish as early as possible the best way might be to have a thread that calls #removeStaleValues periodically, right?
Yes, that is correct. But I would not overdo it, there is a real cost to this operation (scanning everything). In general I think it is better to amortise the cost over multiple operations.
Sure. The reason to do is to remove the strong reference to the object. But it is just a test and I might not need it. Thanks! norbert
Norbert
HTH,
Sven
On 28 Jul 2014, at 13:48, Norbert Hartl <norbert@hartl.name> wrote:
I try to give Neo-Caching a shot in a project of mine. Neo-Caching does not have a metacello configuration. If I add the package via versionner the package is added but without repository information. That fails on loading?
How to do? Bug?
Norbert