Say, do you plan on static output from Embperl or only dynamic for
embperl docs? It doesn't make much sense to serve static content
dynamically, resource wise of course.
Most things will be static and pregenerated, like you plan it for the
mod_perl site. There maybe a small dynamic part,
Well, the code is quite crude yet, and it's hard to modularize before
you know what to plan for, but yes the rendering engine is a separate
thing. So after generalizing it and making it pluggable it should be
possible to use other rendering modules.
I will take a look at it when you
Most things will be static and pregenerated, like you plan it for the
mod_perl site. There maybe a small dynamic part, where people are able
to
add links, examples, news etc.
that would be a very good thing to have! The problem is providing the
required setup on apache.org.
For the
