<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
something worth plsying with, is to stick to the fact that the module is served a configsource, but elaborate a bit on how that source is constructed.<BR>
<BR>
The module interface could, for example, expose a 'Get Default Config Source' function that the module manager could use. This could be broken down into "Get Default Config File Name".<BR>
<BR>
UNLESS, and this is the interesting part, the module manager is configured to factor config sources from say http or database - nini has a lot of sources. then suddenly, the config source could be a lookup from a database on machine name field and/or module name field.<BR><BR>
So, I think one of the reasons we chose nini was to be able to make confuration configurable, so to speak.<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR> <BR>Join the 3d web revolution : <A href="http://tribalnet.se/">http://tribalnet.se/</A><BR> <BR><BR><BR><BR><BR>> Date: Thu, 13 Nov 2008 17:00:06 +0000<BR>> From: jjustincc@googlemail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] hypergrid status<BR>> <BR>> Diva Canto wrote:<BR>> > I did exactly that (or something similar) for the traffic simulation and <BR>> > other modules I'm developing for this urban planning startup, Encitra. <BR>> > Encitra is a collection of modules, and they all share a common data <BR>> > repository that include, among many things, xmls of objects and the ini <BR>> > file.<BR>> > <BR>> > So I don't think you need to do something there. We just need to explain <BR>> > better that module config files can be separate. Independent app modules <BR>> > like Encitra definitely should not be in OpenSim.ini. Middleware-ish <BR>> > things probably shouldn't be there either. Apache at some point started <BR>> > separating the config files of its different modules, too. We could do <BR>> > something like that.<BR>> <BR>> Sounds good to me. I suppose my first thought is whether individual modules should (a) be responsible for knowing where <BR>> their own config files are or (b) whether OpenSim should tell them where to load them.<BR>> <BR>> The disadvantage with OpenSim telling them is that they end up having to be in a well known place (perhaps bin/<module <BR>> name>/conf or simply bin/conf/<module name>.ini (or .xml). This also envisages moving OpenSim.ini to <BR>> bin/conf/OpenSim.ini. The advantage is that having configuration modules always in well known places enhances ease of use.<BR>> <BR>> The disadvantage with the modules knowing is that it has to be in some well known place for that module which the base <BR>> OpenSim may disagree with. However, this is an easier route if modules wish to share the same config file (as your <BR>> Encitra modules do).<BR>> <BR>> Either way, the responsibility for disabling/enabling modules would rest with the master OpenSim.ini (rather than with <BR>> individual modules as it does at the moment).<BR>> <BR>> I had a brief look at Apache configuration but it wasn't obvious to me how it was actually being done (beyond the <BR>> standard httpd.conf file, which it sounds like was separated into three but then was put back together again).<BR>> <BR>> > <BR>> > Michael Wright wrote:<BR>> >> I guess we should try to come up with some idea what we want from <BR>> >> separate config files. As currently it is completely possible and <BR>> >> quite easy for modules to load their own ini files by using Nini. Is <BR>> >> that enough or do we want more.<BR>> >><BR>> >> */Justin Clark-Casey <jjustincc@googlemail.com>/* wrote:<BR>> >><BR>> >><BR>> >><BR>> >> I think to some extent this is also pending a revision of the<BR>> >> region module system to make it easy to plug in external<BR>> >> modules with their own configuration files (OpenSim.ini.example is<BR>> >> getting to be a monster). Of course, we've been<BR>> >> saying that for ages now - consider it a long feature lead up :)<BR>> >><BR>> >><BR>> >><BR>> >> ------------------------------------------------------------------------<BR>> >><BR>> >> _______________________________________________<BR>> >> Opensim-dev mailing list<BR>> >> Opensim-dev@lists.berlios.de<BR>> >> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> >> <BR>> > <BR>> > <BR>> > ------------------------------------------------------------------------<BR>> > <BR>> > _______________________________________________<BR>> > Opensim-dev mailing list<BR>> > Opensim-dev@lists.berlios.de<BR>> > https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> <BR>> <BR>> -- <BR>> justincc<BR>> Justin Clark-Casey<BR>> http://justincc.wordpress.com<BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></body>
</html>