12 Apr
2010
12 Apr
'10
10:51 a.m.
On 04/12/2010 03:50 AM, marius zbihlei wrote:
Alex Balashov wrote:
That would certainly solve the problem!
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
Hi Marius,
On 04/10/2010 02:19 AM, Marius Zbihlei wrote:
Hello Alex,
How about a syntax like
modparam("*", "db_url", ...) ?
meaning that it matches all modules that have a db_url param. Maybe this
will also benefit something like module specific log level(when will be
implemented) and other common parameters. Hello Alex,
I agree, this is possible, but I find it an inelegant solution; it
still requires me to anticipate every conceivable module that could be
loaded elsewhere in the configuration, and this is not as easy as it
sounds given its highly flexible, indeterminate nature. It's also just
not pretty. Thus, it is not possible
in advance to know which modules will be loaded, nor possible to
iterate through some list and combine them into a string, so I
cannot do:
modparam("mod1|mod2|mod3", "db_url", ...)
Regarding the modparam statement, I think you can. Unfortunately, I
can't test it a.t.m., but as far as I remember I think the modparam
statement succeeds even if only one of the modules listed in the module
section is configured correctly. For example you can have something like
modparam("carrierroute|xyz", "db_url", ....)
and work, even if xyz module doesn't exist (yet).