So something I didn't actually investigate when I accepted these patches is whether or not it is possible to configure each cache region (ie. the individual cache for each class/collection) to use different cache expiration policies. By the looks of things, the current implementations will use the same configuration properties for all classes. This is not sufficiently flexible for many usecases.
With JCS, it is possible to specify a different configuration for each named region in the one config file. It looks like this is not possible with oscache, or swarmcache, so what I would suggest is that we adopt a convention where oscache-foo.Bar.properties is the properties file for the oscache region foo.Bar. Then, perhaps, oscache.properties would be a "fallback" with defaults, in case there is no config for that specific region.
Perhaps we should also allow properties to be specified in the <cache> element, but I don't like this, it starts to pollute the mapping file with deployment-specific stuff.
We need to address this before 2.1 goes final.
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
