> What if you have many short TTL pieces, all with separate TTLs? That no > longer becomes an easy alternative, but it does stay ugly :-). As I was > thinking about this last night I realized that it would be more correct > to have the template itself specify its Town TL.
What about its Country TTL? > Why should an outer > template know the TTL of an inner template? Unfortunately, this almost > certainly means that the caching would need to be more tightly integrated > with TT than a plugin. Maybe an idea for v3? There's no getting around the fact that if you want to honor shorter TTLs of templates inside of a longer TTL template, you have to leave some code (at least an include) unresolved and uncached until request time. This is equivalent to breaking up the enclosing template by hand. If you don't do that, you have to re-process the longer TTL template every time the shorter one expires. - Perrin
