Compartilhar via

IsolatedStorageBackingStore Class

  • Artigo
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.

Implementation of IBackingStore that stores its CacheItems into IsolatedStorage.

Namespace:  Microsoft.Practices.EnterpriseLibrary.Caching.BackingStoreImplementations
Assembly:  Microsoft.Practices.EnterpriseLibrary.Caching (in Microsoft.Practices.EnterpriseLibrary.Caching.dll)

Syntax

'Declaration
<ConfigurationElementTypeAttribute(GetType(IsolatedStorageCacheStorageData))> _
PublicClassIsolatedStorageBackingStore _
    Inherits BaseBackingStore

[ConfigurationElementTypeAttribute(typeof(IsolatedStorageCacheStorageData))]
publicclassIsolatedStorageBackingStore : BaseBackingStore

[ConfigurationElementTypeAttribute(typeof(IsolatedStorageCacheStorageData))]
publicref classIsolatedStorageBackingStore : public BaseBackingStore

publicclass IsolatedStorageBackingStore extends BaseBackingStore

Remarks

This class assumes a tree-structured storage schema. Each named instance of an Isolated Storage area creates a separate, top-level directory in Isolated Storage. This is to allow a user to segregate different areas in Isolated Storage to allow multiple applications to use their own logically separate areas. Inside each of these areas, each CacheItem is stored in its own subdirectory, with separate files in those subdirectories representing the different pieces of a CacheItem. The item was split like this to allow for several optimizations. The first optimization is that now, the essence of a CacheItem can be restored independently of the underlying value. It is the deserialization of the value object that could conceivably be very time consuming, so by splitting it off into its own file, that deserialization process could be delayed until the value is actually needed. The second optimization is that we are now able to update the last accessed time for a CacheItem without bringing the entire CacheItem into memory, make the update, and then reserialize it.

Inheritance Hierarchy

System.Object
  Microsoft.Practices.EnterpriseLibrary.Caching.BackingStoreImplementations.BaseBackingStore
    Microsoft.Practices.EnterpriseLibrary.Caching.BackingStoreImplementations.IsolatedStorageBackingStore

See Also

IsolatedStorageBackingStore Members

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.