Okay, I think there is still some confusion here as to what I am shooting
for. Ideally, I would like a system where the static parts of the page are
cached. I have recieved several mails suggesting that items such as the
header/footer can be turned into compiled print() statements as part of
the
Jauder Ho <[EMAIL PROTECTED]> writes:
> 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 po
> > 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.
>
> An improvement to the technique used by HTML Tree is to
> "collapse" the non-dynamic portions of an HTML file into
Jauder Ho wrote:
>
> the time/chance to implement such a system, it certainly looks like an
> interesting method of doing things. XML+XSLT is an interesting combination
> but integrating that into a dynamic generator (perl based or other) is
> going to be nontrivial to say the very least. Is ther
On Thu, 27 Jul 2000, Jauder Ho wrote:
> The template may be kept in memory but it needs to be reparsed to
> insert real values, no?
No. With most of these systems it turns into a bunch of "print" calls and
then into a bunch of perl opcodes, so it gets executed each time but not
parsed.
> What I
Cool, I will definitely look further into this. Time to google...
--Jauder
On Thu, 27 Jul 2000, Kip Hampton wrote:
> Jauder Ho wrote:
>
>
> > XML+XSLT is an interesting combination
> > but integrating that into a dynamic generator (perl based or other) is
> > going to be nontrivial to say th
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.
An improvement to the technique used by HTML Tree is to
"collapse" the non-dynamic por
Jauder Ho wrote:
> XML+XSLT is an interesting combination
> but integrating that into a dynamic generator (perl based or other) is
> going to be nontrivial to say the very least. Is there anyone interested
> in exploring this?
Most of the hard work for this has been done by our own lovely and
--
On Thu, 27 Jul 2000 12:22:26 Jauder Ho wrote:
>
>Watching this discussion has been very interesting, I am all for
>separating the HTML and the code portions and have been unable to think of
>a good solution to this particular problem. I ran across smartworker
>(http://www.smartworker.org)
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
ca
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 believ
We do what you describe with mason all of the time, since one can cache
individual components on their own schedules. If you look at:
http://www.investorama.com/guides/stocks
Everything above "you are here" isn't cached, except for "Who's online
now", which is updated to show a number above a
Watching this discussion has been very interesting, I am all for
separating the HTML and the code portions and have been unable to think of
a good solution to this particular problem. I ran across smartworker
(http://www.smartworker.org) a while ago and even though I have not had
the time/chance
13 matches
Mail list logo
