Gareth Coltman wrote:
>
> Hi,
>
> I need to store lookup tables as I previously mentioned, and the
> TurbineGlobalCacheService seemed perfect for this.
>
> My cache objects need to persist for the entire lifetime of the
> application(ie from startup to shutdown), and this is what's causing
> problems.
>
> 1. I can't work out how I can perform early initialisation - I need to load
> database data into the cache on system startup.
Services are the way to make sure you get early initialisation. Another
simple way is to load the cache in a static initializer in a class that
is used for accessing the cache.
> 2. I want to stop the cache from constantly housekeeping. It's a waste of
> processing for my application.
There is a CachedObject.setTTL(-1) method that will stop the cleaning up
of objects in the cache, but I do not know if it is possible to
eliminate the housekeeping from at least looking for expired objects.
john mcnally
>
> The other thing I would like is to divide my Cache into namespaces (or
> different caches), so I can make the cache return all of a certain type of
> element, without having to iterate through the entire cache.
>
> Has anyone else had to implement something similar?
>
> Gareth
>
> ---------------------------------------------------------------------
> 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]
