[Opensim-dev] Proposal for a cleanup/correction of the region-module system

[Melanie]

I'm not happy with that. I see no evil in the nini references and I 
like the option of using nin for private config files outside of 
OpenSim.ini.

Also, I have several modules that read the config from another 
module, so they need to be able to address sections.

Limiting it like that would take away significant functionality for 
little, if any, gain.

Melanie


Stefan Andersson wrote:
> Actaully, how would y'all feel about a simple abstraction of our own;
> 
>  
> 
> Making an OpenSim.Framework IConfig interface of our own, that just exposes a few, simple config methods, like;
> 
>  
> 
> TValue IConfig.SetConfigValue<TValue>(string key, TValue value);
> 
> TValue IConfig.GetConfigValue<TValue>(string key, TValue default);
> 
>  
> 
> Then for each module instantiation the core would just create a 'facade' to the right config source/section (nini or not) - that would be responsible for negotiating config sections and config source (file)name resolution.
> 
> 
> A simple and elegant solution to getting the nini ref out of the region modules.
> 
>  
> 
> While we're at it, why don't we introduce a sibling IConfigBridge that the MODULE is optionally supposed to implement, that could provide simple config negotiation info like;
> 
>  
> 
> string IConfigBridge.GetConfigSectionName();
> 
> string IConfigBridge.GetConfigSourceName();
> 
> Best regards,
> Stefan Andersson
> Tribal Media AB
> 
> 
> 
>  
>> From: adam at deepthink.com.au
>> To: homer.horwitz at gmail.com; opensim-dev at lists.berlios.de
>> Date: Sun, 25 Jan 2009 02:37:01 -0500
>> Subject: Re: [Opensim-dev] Proposal for a cleanup/correction of the region-module system
>> 
>> One other suggested change.
>> 
>> Let's remove IConfigSource from the RegionModule Initialise method - and instead make some kind of globally accessible (via Scene?) .Config. The reason for this is twofold:
>> 
>> 1. We pass config in multiple times, one per scene.
>> 2. It introduces a dependency on Nini that every region module must fill - this is annoying when a module isn't configurable.
>> 
>> Regards,
>> 
>> Adam
>> 
>> > -----Original Message-----
>> > From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-
>> > bounces at lists.berlios.de] On Behalf Of Homer Horwitz
>> > Sent: Saturday, 24 January 2009 12:04 PM
>> > To: opensim-dev at lists.berlios.de
>> > Subject: [Opensim-dev] Proposal for a cleanup/correction of the region-
>> > module system
>> >
>> > Hi all,
>> >
>> > the current system for handling region-modules is slightly broken if
>> > you add/remove regions dynamically (or even for region-restarts). I've
>> > put up some thoughts at
>> > http://opensimulator.org/wiki/New_Region_Modules for discussion.
>> > Please answer on the associated 'discussion' page or here on the list.
>> >
>> > Cheers,
>> > Homer
>> > _______________________________________________
>> > Opensim-dev mailing list
>> > Opensim-dev at lists.berlios.de
>> > https://lists.berlios.de/mailman/listinfo/opensim-dev
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev