On 27-Jul-2000 Jauder Ho wrote:
>
>
> The template may be kept in memory but it needs to be reparsed to insert
> real values, no? What I would like to see is a way to say the template is
> static (header/footer) and does not need to be reparse/regenerated each
> time and comparitively small portion of the page be dynamic. This way, you
> can also store the html on the front end web server or akamize it and
> concentrate on having the app servers provide only the actual data.
The template does not have to reparsed every time. At least with Embperl, the
cached p-code is re-executed but that's it.
If you want to store headers and footers on a seperate machine and wrap them
around dynamic content take a look at my Apache::ProxyStuff module. It doesn't
cache the headers and footers but that feature would be quite easy to add.
> --Jauder
>
> PS. I guess now that I think more about it, we can accomplish this with
> frames but that's a whole other story :)
>
> On Thu, 27 Jul 2000, Perrin Harkins wrote:
>
>> On Thu, 27 Jul 2000, Jauder Ho wrote:
>> > If there was somehow a way to cache say the template, leaving only the
>> > same dynamic portion uncached, it would certainly help things along
>> > quite a bit. If anyone knows of a good way of doing this I would
>> > certainly be interested in hearing it.
>>
>> I believe every single one of the solutions discussed caches templates,
>> most of them as compiled perl code.
>> - Perrin
>>
>>
--
Jason Bodnar + [EMAIL PROTECTED] + Team Linux
Weaseling out of things is important to learn. It's what separates us
from the animals. Except the weasel.
-- Homer Simpson
Boy-Scoutz n the Hood
