[opensource-dev] HTTP viewer map (was: Oh, the drama.)
Thickbrick Sleaford
thickbrick.sleaford at gmail.com
Fri Apr 30 05:56:51 PDT 2010
See http://jira.secondlife.com/browse/SNOW-77
This has been stagnant for too long (incidentally, it was brought up at
yesterday's Snowglobe meeting.)
I think the way forward is standardizing this in a way that allows opensim to
implement it, not going back to UDP, region-local map tiles.
SNOW-77 has a patch attached that handles using a capability to find the base
url for the map tiles, but still sticks to assumptions about the url
structure.
I added a comment there last December, and will repeat it here, that I think
the grid should not just tell the viewer about the base url, but send a
template to prevent depending on a rigid url structure. This looks like
something RUSS can be used for, but that has a dire warning about security
implications of using an untrusted format string:
http://wiki.secondlife.com/wiki/Recursive_URL_Substitution_Syntax
I don't know if this is a problem here (is it?), but I think we should find
*some* way to prevent hard-coding the url structure in the viewer.
On Friday 30 April 2010 14:00:43 Tateru Nino wrote:
> The most obvious solution - from where I'm sitting - is to abstract it,
> and provide different access methods underneath. The higher levels of
> the viewer application should neither know nor care just where the map
> tiles are coming from, beyond making an API call to fetch one. Later,
> one can look at a method by which a grid service might make certain
> representations as to where and how those tiles are located and to be
> fetched, but compartmentalizing the hard-wired knowledge (at this stage)
> seems to be the best option, presently.
>
> On 30/04/2010 8:20 PM, Lance Corrimal wrote:
> > "patching opensim"...
> >
> > ...how do you "patch" the people who provide a service for free, to make
> > them rent an expensive distributed storage provider for their map tiles?
> > are you going to rent S3 yourself, for your own little local grid?
--
Thickbrick
More information about the opensource-dev
mailing list