Updated: June 30, 2012
Specifies the way locally cached objects should be invalidated.
Assembly: Microsoft.ApplicationServer.Caching.Core (in Microsoft.ApplicationServer.Caching.Core.dll)
Specifies that objects will stay in local cache until they are automatically invalidated by a cache notification. Not supported in Windows Azure Shared Caching.
Specifies that objects will stay in local cache until their lifetime reaches the localCacheTimeout duration specified in the DataCacheFactory constructor.
When using the TimeoutBased enumeration to specify local cache sync policy, once objects are downloaded to local cache, they will stay there until they reach the object timeout value specified in the DataCacheFactory constructor's localCacheTimeout parameter. When the objects reach the time-out value, they are invalidated so that each object can be refreshed from the cache cluster the next time that it is requested.
When using the NotificationBased enumeration, locally cached objects will be automatically invalidated by cache notifications. The object lifetime can only be as short as the notification polling interval specified by the DataCacheFactory constructor's pollInterval parameter.
Notifications are not supported in Windows Azure Shared Caching. Windows Azure Shared Caching must use TimeoutBased invalidation.
In order for your application to use notifications, you need to enable them on a named cache. In Microsoft AppFabric 1.1 for Windows Server Caching, use the notificationsEnabled parameter with the New-Cache or Set-CacheConfig Windows PowerShell commands. In Windows Azure Caching, enable notifications in the Caching configuration of the role that hosts the cache.