Joshua Chamas wrote:
>
> I would recommend using Apache::ASP as it does everything you need.
> First it allows for creation of your dynamic tags:
>
> http://www.nodeworks.com/xml.html
>
> It will reload all of your templates dynamically at runtime, for
> ease of development but also has advanced server startup parent
> httpd compilation abilities for greatest scalability, where templates
> are shared across child forks:
>
> http://www.nodeworks.com/asp/tuning.html#Precompile%20Scripts
>
> Finally, it will give your designers a comfortable ASP scripting
> environment, while giving you the developer powerful APIs like
> the Script_OnStart event which you can use to customize the
> global environment available to each script:
>
> http://www.nodeworks.com/asp/events.html#Script_OnStart%20%26%20Script_OnEnd
>
> If you think its scarey that designers might be able to execute
> arbitrary perl code in <% %> blocks, I have thought about allowing
> a config option to turn these blocks off, so the compiler will
> just strip them or render the raw code by default. Might be like
>
> PerlSetVar CodeBlocks 0
>
> This way, your designers would only be able to use the custom tags
> that you provide for them.
Thanks Joshua
I was aware that Apache::ASP did all the some of these things but not
all of this - and I see you will be including some XML support .... I am
truely impressed (the caching bit, and the script environment changes).
My aims have thus far been to write my own modules that just do what I
need and no more, so that Firstly its efficient (no excess code, not to
say Apache::ASP has any of that ;-), and Secoundly to learn some more.
This does mean I reinvent the wheel code wise, compared to projects like
yours, HTML::Embperl, HTML::Template - but I'll learning in the mean
time. I am not expecting to release anything on CPAN or for the code to
be used by anyone else.
If anything I've been introduced to HML::Template - which is just the
lightwieght templating module that would help with my present (work)
project (I'd use my own module, but using a maintained CPAN module
would be better for my clients in the long term (i.e after I've left)).
Thanks again for the pointer.
Greg Cope
>
> -- Joshua
> _________________________________________________________________
> Joshua Chamas Chamas Enterprises Inc.
> NodeWorks >> free web link monitoring Huntington Beach, CA USA
> http://www.nodeworks.com 1-714-625-4051
