[Opensim-users] Consequences of vicinity

[Charles Krinke]

Hang on. We are getting afield a bit. There are several goals and tests going on in OSGrid that have nothing to do with HyperGrid.

One of these is developing a mainland, which by its nature needs sims side by side.Another is testing region crossings at sides and corners, which also by its nature needs sims side by side.

I admire and respect Diva's work, but lets also not loose sight of the other considerations that led to us creating a grid in the first place.

Those who wish to work on HyperGrid notions may certainly put their regions away from the growing mainland at 10000,10000. I believe that the area less then 4096, 4096 may be more suitable for HyperGrid notions as it bypasses the "4096 arithmetic problem" in the client.

Charles




________________________________
From: Justin Clark-Casey <jjustincc at googlemail.com>
To: opensim-users at lists.berlios.de
Sent: Tuesday, December 30, 2008 8:33:29 AM
Subject: Re: [Opensim-users] Consequences of vicinity

Diva Canto wrote:
> Justin Clark-Casey wrote:
>> Is it worth updating the interface version number in OpenSim.Framework.Servers.VersionInfo to ensure that this is 
>> enforced automatically for grids?
>>
>>  
> Yes, to some extent, but not completely. This is about sim-sim comms, 
> not sim-grid comms. Therefore if you have a running sim connected to 
> osgrid who's owner is on vacation, that sim will continue to run -- and 
> maybe cause problems to the neighbors -- even if you bump up the version 
> number in Servers. We would need to check the version number on 
> inter-region comms, not just on region registration with the grid. Or 
> else on region registration, the grid server should look into the 
> VersionNumber of the potential neighbors and warn/disallow registrations 
> when the version numbers are not compatible.

In principle, a grid server that has been upgraded could, on restart, kick off regions that have an interface number 
that is now too low.  This would be for a grid administrator that wants to ensure a smooth inter-region experience on 
the grid.

In practice, a grid administrator might want to be more lenient (perhaps notification rather than kick).

I guess you could have a grid that allows different clusters of regions where those regions use a different/old 
interface than other region clusters on the grid, yet all clusters used the same grid comms.  The problem of teleport 
(in which you still travel between disconnected clusters) might require a different interface version than an interface 
for neighbouring sims.

Nonetheless, in practice people who don't read these lists will continue to put sims side by side.  If the version 
number isn't bumped we may well see an upsurge in questions and confusion which we saw not long ago when OpenSim 
revisions crossed interface incompatibility thresholds (whether grid <-> sim or sim <-> sim).

Perhaps this is something that grid admins can give input on.  Do you think the interface version number should be 
bumped with neighbour interface changes to stop people having problems when they are neighbouring regions with 
incompatible versions?  Or should people always be instructed to keep regions away from each other unless they are sure 
that their neighbours are going to update in sync with themselves.

-- 
justincc
Justin Clark-Casey
http://justincc.wordpress.com
_______________________________________________
Opensim-users mailing list
Opensim-users at lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-users/attachments/20081230/5b66f8b0/attachment.html>