Table of Contents

Namespace ToSic.Eav.DataSources.Caching

DataSources need various kinds of caching mechanisms, like...

  • to cache the AppState once loaded
  • to cache resulting streams in a cpu intensive query

The Caching system is in charge of all this, and will also take care of clearing caches as well as updating downstream caches if an underlying source has been updated.


  1. Introduced in 2sxc 04.00



Special DataSource which automatically caches everything it's given. It's Used to optimize queries, so that heavier calculations don't need to be repeated if another request with the same signature is used.
Internally it asks all up-stream DataSources what factors would determine their caching. So if part of the supplying DataSources would have a changed parameter (like a different filter), it will still run the full query and cache the results again.