<html><head>
<meta content="text/html; charset=ISO-8859-15" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">I do not speak about a
paradigm change (OpenSim as is, is super and the progress you developer
are showing, is tremendous) - i only speak about the possibility, to
extract specific configuration sections into separate files. Maybe it is
possible (you mentioned, that it can be done by the admin?!). Thats's
all, what needed. Maybe only a hint to the explanation of this
possibility and a how to is enough? As I said - maybe I missed
something?<br>
<br>
But, of course, I only speak for me and myself and that's only my
outcome of my experience.<br>
<br>
Markus<br>
<br>
<blockquote style="border: 0px none;"
cite="mid:4E8B494F.1030008@t-data.com" type="cite">
<div style="margin-left:40px"><hr style="border:none 0;border-top:1px
dotted #B5B5B5;height:1px;margin:0;" class="__pbConvHr"><br></div>
<table style="padding-top: 5px;" class="__pbConvTable">
<tbody><tr><td style="padding-top:4px;" valign="top"><img
src="cid:part1.07000404.05040401@secondlearning.de"
photoaddress="melanie@t-data.com" photoname="Melanie"
name="compose-unknown-contact.jpg" height="25px" width="25px"></td><td
style="padding-left:5px;" valign="top"><a moz-do-not-send="true"
href="mailto:melanie@t-data.com" style="color:#2057EF
!important;text-decoration:none !important;">Melanie</a><br><font
color="#888888">4. Oktober 2011 19:58</font></td></tr></tbody>
</table>
<div style="color:#888888;margin-left:35px;" __pbrmquotes="true"
class="__pbConvBody"><br><div>The way the system is working now means
the user can merge a working<br>configuration and then edit only a
subset. There is no need for a<br>paradigm change because the goal is
already achievable. It doesn't<br>do this out of the box but can easily
be made to do it by the admin<br>of the system. Grids are too different
from each other to<br>accommodate their hypothetical needs in the base
distro.<br><br>Melanie<br></div><div><!---->_______________________________________________<br>Opensim-dev
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br><a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br><br><br></div><hr
style="border: none 0;border-top:1px dotted
#B5B5B5;height:1px;margin:15px 0 0 0;" class="__pbConvHr"><br></div>
<table style="padding-top: 5px;" class="__pbConvTable">
<tbody><tr><td style="padding-top:4px;" valign="top"><img
src="cid:part1.07000404.05040401@secondlearning.de"
photoaddress="info@secondlearning.de" photoname="Markus Metzmacher"
name="compose-unknown-contact.jpg" height="25px" width="25px"></td><td
style="padding-left:5px;" valign="top"><a moz-do-not-send="true"
href="mailto:info@secondlearning.de" style="color:#2057EF
!important;text-decoration:none !important;">Markus Metzmacher</a><br><font
color="#888888">4. Oktober 2011 18:24</font></td></tr></tbody>
</table>
<div style="color:#888888;margin-left:35px;" __pbrmquotes="true"
class="__pbConvBody"><br>
<meta content="text/html; charset=ISO-8859-15" http-equiv="content-type">
Dear All,<br>
<br>
I've a question regarding the OpenSim.ini, *Common.ini, etc. These ini
files are heavily influenced by the implementations and developments you
make. Some parameters never change (i.e. Database settings, Group
settings etc.) but others do.<br>
<br>
Is it possible, to inject the code, which is more static by including
files? Example: the port, which is used for a region/simulation is
configured in the [Network] section and never changes because, once it
is running on this port, you will never change it - especially if you
host regions on one server. I think, it might be a good idea to call a
separate (static) file <span style="font-style: italic;">like</span>
'include network_section "path/network.ini"' to inject the code like you
do to distinguish between HyperGrid, Standalone, etc.<br>
<br>
The user (Grid Admin or, if on another server and allowed by the Grid
Admin, the region admin) then has only to enable/disable the features in
the (new) OpenSim.ini without taking care about the settings, which
depends on that specific region like database, port , groups, etc ...<br>
<br>
In fact, this will reduce upgrade times needed for upgrading a full grid
from day's to hours. Especially most tasks can be automated. Maybe this
option is available today (i don't know) but if not, it might be a good
idea to implement it? If I missed something, perhaps only a hint of
this possibility is missing on opensimulator.org?<br>
<br>
Also, I think, the possibilities of the switches within ROBUST.ini are
not that good described. I do not know, if robust.ini is the file, which
plays the only role for the asset/inventory/user..... server
environment. Does OpenSim.ini plays a role for robust server only as
well? <span>I think, others are puzzling exactly the same. </span><br>
<br>
What do you think? Sorry - if there's a better place, to place my
questions, please tell me.<br>
<br>
With kind Regards<br>
Markus<br>
<div>_______________________________________________<br>Opensim-dev
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br><a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br></div></div>
</blockquote>
</body></html>