public override void SetupInvalidation(FederationCacheManager manager, string key)
{
}
public override void SetupInvalidation(FederationCacheManager manager, string key)
{
manager.AddKeyToInvalidateOnTopicsInNamespaceChange(key, Namespace);
/// For now we take a very aggressive invalidation approach that says that whenever
/// the list of namespaces changes, we invalidate all cached topic lists. This is because
/// we dont' yet do the work to be more granular (e.g., figure out when a namespace is added
/// or removed exactly which namespaces are impacted). This will likely cause a near flushing of
/// the cache when namespaces are added or removed, but that should be pretty rare. if it
/// becomes a serious problem, we can enhance this to be more granular.
manager.AddKeyToInvalidateOnFederationNamespacesChange(key);
}
public override void SetupInvalidation(FederationCacheManager manager, string key)
{
foreach (CacheRule each in _Children)
each.SetupInvalidation(manager, key);
}
/// <summary>
/// Enable caching for this federation and use the supplied IFederationCache as the underlying store for
/// the caching. By using this method, you can pass in a cache that's smarter about memory allocation and
/// resource utilization than the GenericCache used by default.
/// </summary>
/// <param name="aCache"></param>
public void EnableCaching(IFederationCache aCache)
{
_FederationCacheManager = new FederationCacheManager(this, aCache);
}
public override void SetupInvalidation(FederationCacheManager manager, string key)
{
manager.AddKeyToInvalidateOnFederationNamespacesChange(key);
}
