Thomas Dudziak wrote:
'short' in the example is just some name/id that the user defined for
one class in the longevity classification. It could also have been
called 'John' or something :-)
You're right though that cache-class would not be a good name, perhaps
cache-level or similar would be better ?
cache-timeout (or similar) would be my choice, since 'level' is already
associated with one-level vs two-level cache.
Where I have seen the need for this, some objects are extremely long-lived
and most others not. Regression tests etc are not concerned about cache
timeouts at all (the cache should be, and is currently, completely transparent)
- HSQLDB or Oracle would use the same object-level caching timeouts.
But perhaps not if you use different caches, i.e. something like
Coherence for the real app and integration testing, and a simpler
cache for development and unit tests. After all you setup the cache
for the target system, and usually the development systems differ from
the target systems, esp. in terms of memory and i/o throughput.
True, then you might want to tweak cache-timeouts per jcdAlias.
As long as one can do both the simple numeric setting and
have the choice of the more advanced 'ref-id' mapping to the jcd,
the configuration covers both scenarios.
Eg:
<class-descriptor ... cache-timeout="1000">
And:
<class-descriptor ... cache-timeout="john"> ;)
+
<object-cache ...>
<cache-class name="john" timeout="100"/>
</object-cache>
I guess the final solution depends on the implementation details
of the code Andrew is about to integrate.
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
