Hi Gareth,
Depending on how complex your needs are you can think about implementing
your own Turbine Service. Turbine Services are singletons that can live
throughout the entire live of the application. You only need to implement
and interface to have it initialized and "finalized". Turbine handles the
instances/initialization/etc. for you so it is fairly easy to implement.
You can for instance create a Turbine Service that creates your cached
object(s) at startup. Your service is then responsible for the rest, but
since you want to reduce the overhead this might be useful to you.
For more information you can look at the o.a.turbine.services package to see
how it is done. If I remember correctly Jason mentioned something about a
texen task that can create a service skeleton for you.
~ Leon
> 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.
> 2. I want to stop the cache from constantly housekeeping. It's a waste of
> processing for my application.
>
> 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]
