[Opensim-dev] e: SimulatorExtraFeatures Service

[James Hughes]

On Fri, 2014-08-01 at 15:43 +0100, Ai Austin wrote:
> At 13:00 01/08/2014, Bluewall wrote:
> >They are launched at a region in a foreign grid, much like
> >teleporting within their home grid. Unless these parameters are
> >dynamically set in the viewer, the user will see the services provided
> >by their home grid,
> 
> 
> Thanks for the explanation Bluewall...  is there a wiki page to 
> assist with setup and typical values?
> 
> I assume the DestinationGuideURI will be a web page similar to what 
> ee can already do for a home grid?  e.g. our Openvue grid guide is served via
> 
> http://virtual.aiai.ed.ac.uk:8002/resources/guide.html
> 

It is one and the same. 


> but the MapServerURI, SearchServerURI are servers without any web 
> page details after them?
> 
> MapServerURI can I assume be the home grid as its served by OpenSim 
> core.  But SearchServerURI needs an add on of some kind to work?
> 

Map - yes, search can be the basic search included in the OpenSim
distribution or the search module with the php backend.

> I am less clear how this links to values I see in [LoginService] 
> which seem also to have MapTileURL, DestinationGuide and even 
> commented out things for AvatarPickerOpenIDServerURL, 
> etc.  ProfileServerURL has a really peculiar template style example. 
> Note some have URL on end, some URI and some nothing.  maybe all this 
> could do with a cleanup?
> 

I agree. Some of this was from some experimental work being done just
prior to Linden Lab cutting the --loginuri from the viewer. I was
working on web profiles integration patches for the viewer and I
abandoned it after the loss of support of Linden Labs. If I can be sure
that no one is using those, I will remove them.


> I even see in OSGrid add on region settings an openSim.ini section 
> specifically for search.. but maybe that for an add-on module fo some kind?
> 
> 
> [Search]
>      SearchURL = http://search.osgrid.org/query.php
> 
> 

Yes, that is the external search module and it's url to the php backend.


There was an opportunity to get viewer support for this, so here is a
quick implementation of the idea that can be tested by users and viewer
developers, and adjusted through iterations until it is the best
possible solution.

As always, thanks for your observations and feedback,
BlueWall