On the apache observation, I think that both are right - the new ways are the new ways, and the old ways still work, but new ways are preferred.<br><br><div class="gmail_quote">On Thu, Nov 13, 2008 at 11:00 AM, Justin Clark-Casey <span dir="ltr"><<a href="mailto:jjustincc@googlemail.com">jjustincc@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">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>
</div>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>
<div class="Ih2E3d"><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 <<a href="mailto:jjustincc@googlemail.com">jjustincc@googlemail.com</a>>/* 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>
>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
>><br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
<div class="Ih2E3d">><br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br>
<br>
</div><div class="Ih2E3d">--<br>
justincc<br>
Justin Clark-Casey<br>
<a href="http://justincc.wordpress.com" target="_blank">http://justincc.wordpress.com</a><br>
_______________________________________________<br>
</div><div><div></div><div class="Wj3C7c">Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>===================================<br>The wind<br>scours the earth for prayers<br>The night obscures them<br><br><a href="http://osgrid.org">http://osgrid.org</a><br>
<a href="http://del.icio.us/SPQR">http://del.icio.us/SPQR</a><br><a href="http://twitter.com/jstallings2">http://twitter.com/jstallings2</a><br><a href="http://www.linkedin.com/pub/5/770/a49">http://www.linkedin.com/pub/5/770/a49</a><br>