• Task
  • Status: Resolved
  • 1 Critical
  • Resolution: Fixed
  • ljacomet
  • Reporter: cdennis
  • January 22, 2013
  • 0
  • Watchers: 3
  • March 01, 2013
  • February 15, 2013


Since there is now only one concrete subclass of ElementEvictionData which is shared by both clustered and unclustered caches we can safely do away with the entire ElementEvictionData concept and instead inline the various timestamp data in to the Element class.


James House 2013-02-15

This needs to get into the FCS release since it has an API change.

Louis Jacomet Jacomet 2013-02-15

* Removed ElementEvictionData * creationTime and lastAccessTime are now fields inside Element * Element API methods linked to these field have the same behaviour * clone and serialization behaviour are preserved for Element class

API change: {{(get set)ElementEvictionData}} removed from Element