Re^3: RFC: Templating without a System

Thank you for giving HTML::Seamstress serious consideration. I too was worried about performance at production level... what I did was pre-parse the HTML file before each web request.

I looked around on CPAN for a singleton caching solution, but nothing really fit, so what I did was call Webpage::PackageName->new() and store the results in a cache key ahead of time. The module for caching is Class::Cache. Like I said, I didn't want to write it but it was necessary.

Comment on Re^3: RFC: Templating without a System Download Code

Replies are listed 'Best First'.
Re^4: RFC: Templating without a System by shmem (Chancellor) on Jun 23, 2006 at 15:13 UTC
As you may have seen from my benchmarking code I was not re-parsing the HTML, every time round, but only calling `process` with a pre-parsed tree. You're in a fix here. Parsing HTML to a DOM tree gives you the freedom to manipulate every branch and twig and content as you like, but at the cost of speed. If you cache the modified tree or parts of it, you give away that freedom, as if you hadn't had it in the first place. If if you have fixed places where elements are altered - as with your example pages produced from `spkg.pl`, there is no difference to static pages with inline perl as with Mason or with my approach. In the sub process of spkg.pl-generated pages the names are even static: `sub process { my ($tree, $c, $stash) = @_; use Data::Dumper; warn "PROCESS_TREE: ", $tree->as_HTML; # $tree->look_down(id => $_)->replace_content($stash->{$_}) # for qw(name date); $tree; }` [download] To have freedom of which node has to be altered with which value, the key/value pairs should be taken from `$stash`. But then, again, caching is ineffective. That's why I think HTML::Seamstress is ok for template generation but not actually for serving pages. regards, --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: RFC: Templating without a System
by shmem (Chancellor) on Jun 23, 2006 at 15:13 UTC

process

You're in a fix here.

Parsing HTML to a DOM tree gives you the freedom to manipulate every branch and twig and content as you like, but at the cost of speed. If you cache the modified tree or parts of it, you give away that freedom, as if you hadn't had it in the first place.

If if you have fixed places where elements are altered - as with your example pages produced from spkg.pl, there is no difference to static pages with inline perl as with Mason or with my approach.

In the sub process of spkg.pl-generated pages the names are even static:

sub process {
  my ($tree, $c, $stash) = @_;

  use Data::Dumper;
  warn "PROCESS_TREE: ", $tree->as_HTML;

  # $tree->look_down(id => $_)->replace_content($stash->{$_})
  #     for qw(name date);

  $tree;
}
[download]

To have freedom of which node has to be altered with which value, the key/value pairs should be taken from $stash. But then, again, caching is ineffective.

That's why I think HTML::Seamstress is ok for template generation but not actually for serving pages.

regards,
--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

[reply]
[d/l]
[select]