Re: [Webmacro-devel] Template based config - a benefit

[Keats <ke...@su...>]

I agree.  If we can use the concurrentMap to enable dynamically deploying various types of plugins, then the template mechanism could give us a lot of power.

You would have to have some sort of bootstrap configuration that would allow you to evaluate the config template.  Then you could do nice things in the template like:

#include 'standard-directives-init.wm'
#include 'standard-tools-init.wm'

#if ($ServletMode){
  #include 'servlet-tools.wm'
}

etc ...

Plus we could detect changes and update the configuration at runtime (with a bit of work).

Obviously this would take some discussion -- I don't know if we could do this for 2.0, but maybe 2.5?

Keats



-------Original Message-------
From: Marc Palmer <ma...@an...>
Sent: 07/28/03 05:07 PM
To: web...@li...
Subject: [Webmacro-devel] Template based config - a benefit

> 
> 
Just a thought to throw in.

Template-based config would be very very very good because it would allow 
people to #include common config elements from other projects.

Thus, it would allow modularisation of config. Template X has a list of
all 
directives in it, Template Y has a list of tools to load, Template Z has a 

list of functions and so on.

This way you can mix and match your environment.

I seem to remember this idea of templates for config being raised quite a 
few months ago and I think I was against it. I'm warming to it.



-- 
Marc Palmer