<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:12pt"><div>I would urge us to make changes to the master avatar stuff with notice and encouragement of folks to write FAQ, wiki entries, mini-apnotes and anything else that will help cut down on confusion of those who have significant effort invested into builds on existing regions.<br><br>Charles<br></div><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Melanie <melanie@t-data.com><br><b><span style="font-weight: bold;">To:</span></b> diva@metaverseink.com; opensim-dev@lists.berlios.de<br><b><span style="font-weight: bold;">Sent:</span></b> Wednesday, April 29, 2009 1:52:47 PM<br><b><span style="font-weight:
bold;">Subject:</span></b> Re: [Opensim-dev] moving away from grid vs. standalone<br></font><br>
I have done a lot of stuff related to that. Master avatar should not <br>even exist in the way it still does today, that is legacy. The very <br>same thing can be done in another way (code-wise).<br>So the existing master avatar stuff can be removed,if that is the <br>only blocker, i'll think up some new semantics for that and <br>implement it.<br><br>Melanie<br><br><a ymailto="mailto:diva@metaverseink.com" href="mailto:diva@metaverseink.com">diva@metaverseink.com</a> wrote:<br>> I think that there is a technical obstacle to doing that: the master <br>> avatar stuff, that happens early on in the application (OpenSimBase, <br>> line 688), needs to have the communication code in place. I think -- <br>> although I may be wrong -- that that happens before region modules are <br>> in place.<br>> <br>> Melanie wrote:<br>>> I still think all that stuff can be put in region modules....<br>>> <br>>> Melanie<br>>>
<br>>> <a ymailto="mailto:diva@metaverseink.com" href="mailto:diva@metaverseink.com">diva@metaverseink.com</a> wrote:<br>>>> Maybe the right name for it is<br>>>> OpenSim.Region.ResourceServicesConnectors.dll<br>>>><br>>>> <a ymailto="mailto:diva@metaverseink.com" href="mailto:diva@metaverseink.com">diva@metaverseink.com</a> wrote:<br>>>>> Stefan Andersson wrote:<br>>>>>> How about<br>>>>>> <br>>>>>> ---<br>>>>>> [RegionResourceServices]<br>>>>>> ;GridService = OpenSim.Region.Communications.Hypergrid.dll, <br>>>>>> HGGridServices<br>>>>>> ;GridService = OpenSim.Region.Communications.Local.dll, <br>>>>>> LocalBackEndServices<br>>>>>> <br>>>>>> GridService = OpenSim.Region.Communications.OGS1.dll, OGS1GridServices<br>>>>>>
<br>>>>>> [GridService]<br><span>>>>>> grid_server_url = "<a target="_blank" href="http://192.168.1.101:9000">http://192.168.1.101:9000</a>"</span><br>>>>>> grid_send_key = "null"<br>>>>>> grid_recv_key = "null"<br>>>>><br>>>>> The problem with specifying dlls *in this particular case* is that <br>>>>> these things aren't entirely orthogonal/different. The Hypergrid dlls <br>>>>> are a mashup of the other two. Therefore from a source code <br>>>>> perspective it makes things a heck of a lot more complicated than <br>>>>> they need to be if we simply merge things and use conditionals on <br>>>>> configuration variables. For example, hyperlinks (part of grid <br>>>>> services) is a really simple extension to LocalGrid services.<br>>>>><br>>>>> The issue of local vs remote
services isn't entirely orthogonal <br>>>>> either. Some parts of OGS1 use Local services -- the well know <br>>>>> pattern of trying things locally first and if that doesn't work, <br>>>>> proceed for a remote service call (e.g. OGS1 grid services does that).<br>>>>><br>>>>> I see why you want this, in abstract. If another service comes along, <br>>>>> it can simply be added as a component. Or if someone writes, say, a <br>>>>> completely different inventory service, its interface can be added as <br>>>>> dll.<br>>>>><br>>>>> But in this particular case, for the code we already have, I think <br>>>>> that having Local.dll, OGS1.dll and Hypergrid.dll is not working <br>>>>> well, even if the configuration process is the one you suggest. The <br>>>>> code is mess; things are _way_ more complicated
than they need to be.<br>>>>><br>>>>> So, maybe, what we can do is merging these two ideas. We'll have only <br>>>>> one dll (OpenSim.Region.ResourceServices.dll), but we'll specify <br>>>>> things in OpenSim.ini the way that you suggest, so that if anyone <br>>>>> comes along and wants to plug in a different inventory service, he <br>>>>> can just specify the other dll and an entry class name for it.<br>>>>><br>>>>> What do you think?<br>>>>><br>>>>><br>>>>>> [Security]<br>>>>>> <br>>>>>> SessionAuthentication = {True|False}<br>>>>>> KeyAuthentication = {True|False}<br>>>>>><br>>>>>> ---<br>>>>>> <br>>>>>> The constructor is being fed a config source, so the service can <br>>>>>> pick
out whatever it needs.<br>>>>>> <br>>>>>> All the shipped grid services could move into one assembly, as we're <br>>>>>> explicitly specifying the implementing calss.<br>>>>>> <br>>>>>> I believe this approach would get us improved flexibility.<br>>>>>><br>>>>>> /Stefan<br>>>>> _______________________________________________<br>>>>> Opensim-dev mailing list<br>>>>> <a ymailto="mailto:Opensim-dev@lists.berlios.de" 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>>>> Opensim-dev mailing list<br>>>> <a
ymailto="mailto:Opensim-dev@lists.berlios.de" 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>> _______________________________________________<br>> Opensim-dev mailing list<br>> <a ymailto="mailto:Opensim-dev@lists.berlios.de" 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>Opensim-dev mailing list<br><a ymailto="mailto:Opensim-dev@lists.berlios.de" 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></div></body></html>