On Tue, May 02, 2006 at 05:17:11PM +0200, Jochem Maas wrote:
[...]
>
> hopefully you see that it's not your docs at fault so much as I have got a
> rather complex codebase and I'm finding it:
>
> a, hard to fully understand the compiling/caching paradigm in smarty per se
>
> and
>
> b, harder still to take the examples in the docs and extrapolate the
> concepts
> into a design for flexible,generic production quality caching mechanism
> which
> i can actually implement (and would work: in terms of the clients'
> requirements
> for dynamic content - i.e. that 'truely' dynamic stuff doesn't get cached,
> etc).

my experience with smarty's caching is, that it's

a, works best if the whole system is built with caching in mind, and
built around smarty's caching mechanisms.

and that you can

b, use any caching with smarty that you like: just leave smarty's
caching off, and fetch the cached contents with your cache logic and
assign them to template variables which are displayed templates.

> regards,
> Jochem.