differnces between template and content caching?

Wednesday 08 October 2003 11:13:34 am

I'm noticing that when I have content caching enabled, I don't have to clear the cache like I do with template caching. Why is this? I still see the cached content files in the /var directory. When I change content and then refresh my page, the cache also refreshes. So it must know that the content has been updated since the page was viewed last. I think it's important to elaborate on how eZpublish is using caching. Afterall, without caching, eZpublish would be too slow for most production environments.

Thanks for any insight,
Shaun

Thursday 09 October 2003 11:27:20 am

Valentin,
Thanks for your response. I know when I need to clear the cache. I just don't understand how the system knows when content has been updated, but not when templates have been updated. I thought that maybe cache files were removed when an object is updated, but that's not the case. They update when the object is viewed.

-Shaun

Monday 13 October 2003 9:38:50 am

As I understand it, the template cache is only used when building a content page from scratch. The template engine uses the cached, "optimized" versions of your template files to construct a page, then stores that entire page -- template included -- in the content cache.

If you have the template cache disabled, clearing the template cache won't do anything for you. The template is just being cached as part of your output in the content cache.