Caching

StarterKit provides uses Kentico, Katalyst, and a Castle dynamic proxy interceptor to provide data caching that’s easy to use.

• Using the Castle dynamic proxy (i.e., interceptor) any class that inherits from IService or IRepository will automatically use the caching interceptor.

• From those classes, any class methods that return Katalyst TreeNodes, custom table records, or strings will have their results cached.

• Katalyst will automatically create the Kentico cache dummy keys, so that when content is changed any cached content that depends on it will be expired.

Note: You may have had bad luck with cache dependencies in the past, and had to use the system Clear cache function, or the CacheDependencyAttribute frequently. However, a lingering, long-time, Katalyst bug has been fixed. Caching should be much more reliable now.