so maybe at startup it's not a bad idea after all :)
So, does this mean that you don't have a specific objection against deprecating (or tossing) direct access to %Apache::ReadConfig:: in the future in favor of ->add_config("User foo") ?
The problem with add_config() is that it wants a string as if you've written it in httpd.conf language. Taking an access to %Apache::ReadConfig:: away takes away the ability to use perl structs to autovivify complex constructs. e.g. how do you build a complex vhost with nested containers using add_config?
may be we could have an alternative method, accepting an SV (e.g. a hash ref which represents a container) which perl will then convert to a string and feed to add_config?
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
