Idea
page caching+status
page caching+priority
page caching+tag
page caching+issues
For a wagn site to scale, we will need, in many cases, to be able to deliver fully cached pages.
But some kinds of content make this problematic, including:
- searches
- certain contextual names, especially _main and _user
- content with permission restrictions
- views with context-sensitive code
page caching+solution
The basic idea is to cache all parts of the page without one of the "problems" mentioned above and then make separate requests for those. This core of the problem is caching "nests".
The nest cachability test will have three levels:
- cacheable name? - no if _main, _user, etc. otherwise...
- cacheable view? - view can be always, never, or sometimes. if sometimes then...
- cacheable core? - this is a quality of the set. if the core view is cacheable, then all views that depend on the core are, too
Publicly viewable pages can be cached with Varnish.
page caching+discussed in support tickets
page caching+relevant user stories