Michael Matz wrote:


> > An image cache if an obvious solution to this but I doubt we want
> > to use introduce another memory hog..
>
> Hmm... May be a slowly self-cleaning cache is the best. The problem we
> were trying to solve was reducing of startup time, so after the app is
> started, that cache is not that much needed anymore (or at least not in
> that size). But OTOH we are not that of an mem hog.

I'll try this too and see what gives the best results.

Greetings,
Geert