I am trying to understand the purpose of this?
This is not considered to be a replacement for embedded perl solutions
right? It is just a better HTML parser using a visitor design pattern? and
a faster parser than HTML::Parser?
Those are cool motivations, but it takes me a little while going through
your web site to distill this down? Especially because you are putting it
forward as a dynamic web page generation tool.
It's not precisely a dynamic web page generation tool if it is based off of
parsing standard HTML documents. If you wanted to do the same thing you
can do with something like PHP, you'd have to create some pseudo tags even
if they were customized comment tags that are built to be recognized by the
Perl objects implementing the visitor design pattern interface.
Perhaps an example of some of the things you expect people to do with it
(maybe some real world examples) would make it more concrete for me to deal
with as an idea. I apologize for being dense...
Thanks,
Gunther
"Paul J. Lucas" wrote:
> I've implemented what I believe to be a novel technique for
> dymanic web page generation. Although explained in much more
> detail here:
>
> http://www.best.com/~pjl/software/html_tree/
>
> essentially it parses an HTML file into a DOM-like tree where a
> "visitor" function is called for every node in the tree. The
> parser in written in C++ using mmap(2) for speed, but there is
> a Perl XS layer and Apache mod_perl module. Using the Apache
> module, you can bind HTML CLASS attributes to functions via a
> class map that is simpy a Perl hash.
>
> The novel thing about this is that pure, standard HTML files
> are used. This allows one to create a mock-up of the page
> complete with dummy data to see how it will look and then take
> that same page, without modification, and have it used to
> generate dynamic content. The code behind the page is in a
> separate .pm file (that is cached similarly to the way
> Apache::Registry does it).
>
> - Paul
