RE: processing configuration (was) RE: Organisation filtering RE: [Nms-cgi-devel] Anyone...Anyone...?

[Simon W. <es...@ou...>]

On Tue, 2003-02-18 at 11:19, Wizard wrote:
> > OK, that seems to do much the same thing. It just seemed to make sense to
> > do all the config variable procesing in one place but...
> 
> It's not that your idea doesn't make sense, it's just that it is really not
> do-able. We discussed the configuration system earlier, and thought that it
> might be abstracted at some point, so we're keeping it as simple as
> possible.

If you know you're going to be processing a list, it makes sense to
process the list when you read the config file. Then, if you want to use
that list in a second place, you don't have to duplicate the code to
turn a scalar into a list.

If we plan to abstract it, then we really want to make sure that the
code gets what it expects now, and not do further processing in the main
code.

> > ...I'll wait to see the finished code. I'm curious about these user
> > defined variables and how they will be used. I'll wait to read the
> > code/docs and comment further then.
> 
> They're mostly just used as replacement strings for the templates. For
> instance {=NMS_USER_CFG_my_advert=} in the template will take the
> configuration directive:
> USER_CFG_my_advert = <a href="http://mywebsite">Go to my website</a>
> and replace the tag with it. No processing for safety, mind you, just read
> and replace. At some point I may add language-accept & browser ID tags,
> though. It's not in yet, so if you have any objections...

OK, so these will always be scalars. My suggestion still stands but I'll
wait until I see code to comment further.

Simon.