on 10/22/01 3:16 PM, Brett Sanger at [EMAIL PROTECTED] wrote: > I'm (still) in the process of switching our site over to TT. I ran into > the problem where my gut reaction was to PREPROCESS the Header file (which > also loads the leftrail), to POSTPROCESS the Footer file, and to PROCESS > the content file. Thus, our content is completely independant of our > navigation selection. Unfortunately, I ran into problems w/caching (90% > of our site is pre-built and saved as HTML, much as ttree). I was able to > turn caching off (well, after Chris's patch), but that leads me to wonder: > How do others handle dynamic navigation and caching in handlers that > aren't preprocessed, and presumably want caching?
I'm not sure I understand the problem you're having. Most people want their templates to be cached. This has nothing to do with output caching, so a cached template can be used for thousands of different generated pages. Are you having trouble because your content is lots of independent static pages (or pre-generated pages) that are eating up RAM? I had a similar situation with a bunch of static pages that I wanted to add TT headers and footers to. I did it by hacking Apache::SSI to have a #template directive that called TT and I used that for all headers and footers (Apache::SSI doesn't cache pages in memory). This was easy and performed well. Of course the TT directives were only available in the header and footer, but that was fine for this situation. - Perrin
