Magnus ?or Torfason <[EMAIL PROTECTED]> writes:
> I'd like to propose changes to the caching mechanism in Turbine.
>
>
> Rationale:
> Namespace issues mainly. The most logical key
I agree that namespace issues are important, but I still think your second
argument is more important. I don't currently use the cache service in
turbine, but the way I use object caches in other applications I have
different configuration settings for different types of cached
objects. Configuration parameters are typically cache size, expiration
time, cache implementation, cache listeners(who needs to know when the
cache changes) etc. Of course configuration parameters may vary depending
on your actual cache implementation.
I would love to see a new and more reusable Cache module in Turbine. I
would also hope that this could be designed so it can be used directly from
other applications without having Turbine running/configured. The
"staticness" and reliance on TurbineResources have prevented me from using
turbine classes in a few projects.
If you are starting to work on this, I would love to contribute provided
the goal is to come up with a reusable implementation that easily can be
used in Turbine and other frameworks.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
