• New Feature
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • alexsnaps
  • Reporter: steve
  • February 17, 2010
  • 0
  • Watchers: 0
  • May 21, 2010
  • April 07, 2010



Tim Eck 2010-02-17

This can obviously only work if Serializable keys and values are being used.

Since this isn’t a clustered cache, copy-on-read here I assume is for the use case of making it impossible to affect the cache w/o a put()/remove()/etc call. If that is true, this feature really needs to make sure we’re doing copy-on-write too here. We do that in the clustered store just not explicitly. For unclustered we’re going to need to do it explicitly.

Himadri Singh 2010-05-11

ConfigurationFactoryTest covers this issue.