A friend of mine has the exact same problem and I told him to have a look at oscache. The filter aproach could be fine for this, I think. He haven't tried it, though.
Just my 2 cents El Lun, 14-11-2005 a las 21:52 -0800, Patrick Casey escribió: > > I've got a couple of pages that change very rarely, but are > rather expensive to generate (lots of conditional logic, db lookups, etc). > I'd like to have tapestry generate them once, capture the output, and then > either serve them as static pages, or at least serve them out of internal > cache rather than going through the whole render cycle over again. > > > > What's the best way to go about doing this in a Tapestry > friendly fashion? > > > > --- Pat > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
