The template cache caches compiled CFM (and CFC) templates in RAM. What's that got to do with static / dynamic content?
I have used the term the template cache as a synonym of page cache.
Right. So differently from how CF uses the term. That's a bit confusing isn't it?
Template cache doesn't do the caching, as you suggest; it is the cache.
I think you're splitting hairs "a bit" there. What would you call the mechanism that puts the cached CF templates into the template cache then?
If a template's content changes constantly, that is, if it has dynamic content, that will defeat the purpose of Coldfusion caching it. It doesn't matter how or where Coldfusion caches CFM and CFC templates. Caching is for templates that change infrequently or, ideally, that are unchanging or static. The same goes for Coldfusion's caching of connections, queries, etc..
Well yes, I suppose if one is continually writing CFML to templates dynamically before calling them with <cfinclude> or something, it does defeat the purpose of the template cache slightly. This describes a shrinkingly insignificant proportion of template requests though, in any sanely-built system. However the template cache caters for that eventuality as much as it can by weighting the usage of the templates in the cache. If it runs out of space in the cache, it cycles out the least-used templates first.
--
Adam
