> > I'd like to propose changes to the caching mechanism in Turbine.
> >
> > 1 - Multiple caches
> > -------------------
> > Instead of there being a single global cache service, there
> > would be a possibility of creating multiple Caches, each with
> > it's own set of objects in cache. This would be somewhat
> > similar to the way the PoolBrokerService is used.
> >
> > Magnus Torfason
>
> This is similar to what we have done in our project here at e-point
> (which depends pretty heaviliy on in-memory caching of information)
> ...
> Once agreement is reached upon the functinality that the caching
> system should have, I can shedule one of our programers to tailor
> the code we have to Turbine standards, and submit it.
>
> Rafal
What you propose seems perfect for Turbine. I have one thought
about the wrapper class (in turbine it is CachedObject). I like
the fact that in the current Turbine Cache it is the object itself that
determines if it is stale, and the RefreshableCachedObject
class seems very useful to me. This has pros and cons, of course.
It implies that the algorithm for determining staleness
is implemented in the wrapper class, so the Cache itself
cannot select a specific algorithm (since it may contain
many types of wrappers).
Instead it would be possible to specify a default wrapper
class for a given Cache. Objects could then be added
directly to the Cache, using the default wrapper, or
wrapped outside the cache, and added all wrapped and ready.
Magnus Torfason
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
