<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
If we're going to do it 'right' from the start, then obviously, (c) as the general case and (b) as the special case should be the way to go.<BR>
<BR>
(Easy for me to say)<BR>
<BR>
And on a tangent, I'm closing in on having the AssetServer demanding a connection to a user server to resolve user urls. Thoughts?<BR>
<BR>
(It baffles me we don't seem to have that already - I'm not working on the AssetInventory server as I feel its ultimate destiny is still somewhat hazy?)<BR> <BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR><BR><BR><BR> <BR>> Date: Mon, 13 Apr 2009 11:25:06 -0700<BR>> From: diva@metaverseink.com<BR>> To: melanie@t-data.com<BR>> CC: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] Security: multiple or the most generic?<BR>> <BR>> Melanie wrote:<BR>> > Well, if a key is an arbitrary string, then it may also be a constant <BR>> > UUID value, e.g. the standard session id we have now, so (c) really <BR>> > includes (b).<BR>> They are very different. A key is specific for one client-server pair. <BR>> So for each region the client visits there is a unique key that the <BR>> other regions might not know about. When TPs are performed on the <BR>> server-side, this is equivalent to (b) because the regions are acting on <BR>> behalf of the agent. But for client-side Teleports, this makes all the <BR>> difference -- the regions don't know about the other regions' keys.<BR>> <BR>> > [...]<BR>> > So, for now, (c) is the way to go, just don't forget the (b) use case. <BR>> > Interregion trust should remain possible.<BR>> Right. Even though my main focus is the Hypergrid, I'm a little <BR>> reluctant in letting go of (b), and even of (a). The problem I'm <BR>> debating is how to architect OpenSim so that these different schemes can <BR>> co-exist without the code and configuration being a mess.<BR>> <BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR></body>
</html>