A little background:
The purpose of my suggesting this is so that on HG TP into a region, the
Destination Guide URL in the viewer can be switched to one for that
grid, so that when you go to another grid, you can see their guide
instead of your grid's guide (which your viewer is configured with when
you log in. This provides an easy, built-in way for grids to tell you
about their points of interest.
Personally, I think this should stay a grid-level value, that regions
shouldn't be able to override, as then they would/could usurp the grid's
guide. Others had a different opinion.
Sending it to the region then up via the extras, seemed the right way to
do this as this is an optional setting and we already send some optional
things up to the viewer this way. LiruCookies and lkalif are
already/about to implement the viewer side of this, expecting
destination-guide-url to be sent up via the extras.
-ste (smxy)
On 7/30/14, 10:49 PM, Nicky Perian wrote:
imo, I think this should be delivered with grid info. This provides a
cleaner way to handle the URL on the viewer end.
On Wed, Jul 30, 2014 at 7:06 PM, Justin Clark-Casey
<[email protected] <mailto:[email protected]>> wrote:
Hi BlueWall,
I see you added this service to master today which appears to
allow simulators to fetch 'extra' information about OpenSimulator
features at runtime [1]. I have a number of questions/points.
1. Can't this be part of GridInfo? Why do we need another
service for this?
2. Why is the Robust side config named [SimulatorExtraFeatures]?
This makes it a pain to get a uniform config story for standalone
as well as grid. Can't it also be [SimulatorFeatures] so that
standalone doesn't need another seemingly identical section if it
needs to get this config?
3. What is the purpose of the region_override config value? If
regions did want different values for extra features then it would
be trivial for them to workaround this. If these really do need
to be unique to the grid, then I think they should really be
fetched by the viewer directly from the service and not via the
SimulatorFeatures capability, as many of these are not really
simulator features but grid-wide.
4. I know Json RPC was already used for profiles, but it's
getting to be a real pain when services keep using different
access methods (REST, HTTP query parameters, RPC, etc.). Can't we
use HTTP query for this like many of the existing services? [2]
[1] http://opensimulator.org/wiki/SimulatorFeatures_Extras
[2] http://opensimulator.org/wiki/Services
--
Justin Clark-Casey (justincc)
OSVW Consulting
http://justincc.org
http://twitter.com/justincc
_______________________________________________
Opensim-dev mailing list
[email protected] <mailto:[email protected]>
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
[email protected]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
