Share via

BaseBackingStore Members

Include Protected Members
Include Inherited Members

Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

The BaseBackingStore type exposes the following members.

Constructors

  Name Description
Protected method BaseBackingStore
Inherited constructor

Methods

  Name Description
Public method Add

This method is responsible for adding a CacheItem to the BackingStore. This operation must be successful even if an item with the same key already exists. This method must also meet the exception safety guarantee and make sure that all traces of the new or old item are gone if the add fails in any way.
Protected method AddNewItem
Adds new item to persistence store
Public method Dispose Overloaded.
Public method Equals (Inherited from Object.)
Protected method Finalize
Finalizer for BaseBackingStore
(Overrides Object.Finalize().)
Public method Flush
Flushes all CacheItems from backing store. This method must meet the Strong Exception Safety guarantee.
Public method GetHashCode (Inherited from Object.)
Public method GetType (Inherited from Object.)
Public method Load
Loads all CacheItems from underlying persistence mechanism.
Protected method LoadDataFromStore
Responsible for loading items from underlying persistence store. This method should do no filtering to remove expired items.
Protected method MemberwiseClone (Inherited from Object.)
Public method Remove Overloaded.
Protected method RemoveOldItem
Removed existing item stored in persistence store with same key as new item
Public method ToString (Inherited from Object.)
Public method UpdateLastAccessedTime Overloaded.

Properties

  Name Description
Public property Count
Number of objects stored in the backing store

See Also

BaseBackingStore Class

Microsoft.Practices.EnterpriseLibrary.Caching.BackingStoreImplementations Namespace

Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
  • Last updated on