<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This ties in closely with the asset server proposal we’ve
been brainstorming at Intel. The current version of the proposal is at <a
href="http://opensimulator.org/wiki/AssetServerProposal">http://opensimulator.org/wiki/AssetServerProposal</a>
and the project lives at <a
href="http://forge.opensimulator.org/gf/project/assetserver/">http://forge.opensimulator.org/gf/project/assetserver/</a>
(although there is no usable code just yet). <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A large benefit that you gain from bringing the
asset/inventory/etc servers out from behind the simulator is allowing content creators
to manage their own assets, and stop binding end users to a single
grid-provided asset service. Offloading >80% of the traffic from the
simulator is just a side benefit.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>John<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
opensim-dev-bounces@lists.berlios.de
[mailto:opensim-dev-bounces@lists.berlios.de] <b>On Behalf Of </b>Stefan
Andersson<br>
<b>Sent:</b> Thursday, October 30, 2008 2:23 PM<br>
<b>To:</b> opensim-dev@lists.berlios.de<br>
<b>Subject:</b> Re: [Opensim-dev] OSGrid <-> UCIGrid<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>I've been meaning to write a post for a very
long time now. It's in my draft folder. Just not getting it finished.<br>
<br>
First Step:<br>
Just wanted you all to consider what would happen if we, on
ExpectAvatar sent some aux info like 'home user server url', 'home asset
server url' and 'home inventory server url' to be attached to the
ScenePresence, and had all communications interactions use those provided urls.<br>
<br>
What I'm saying is, that the region could accept any avatar in the form of an
authenticated and authorized UUID only, so - "grid" would become
meaningless and "intergrid" becomes a moot issue - all regions would
always expect all clients to come from all different user/asset/inventory
servers. The authorization aspect of the "grid" would then be a
question of service trust, regions clustered under one governing entity
implementing its own trust schemes. One basic trust scheme would probably be
https.<br>
<br>
Next Step:<br>
Consider then, if you will, if the "home" configuration would simply
be a function of a login to your own "home" login server, or simply
as a function of a modified viewer, hence the viewer would send preffered
service url's on login.<br>
<br>
Hey Presto, 3D Web for real. It's not that far away, even given the current
architecture.<br>
<br>
Best regards,<br>
Stefan Andersson<br>
Tribal Media AB<br>
<br>
Join the 3d web revolution : <a href="http://tribalnet.se/" target="_blank">http://tribalnet.se/</a><br>
<br>
<br>
<br>
<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
<hr size=2 width="100%" align=center id=stopSpelling>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'><br>
> Date: Thu, 30 Oct 2008 18:34:21 +0000<br>
> From: jjustincc@googlemail.com<br>
> To: opensim-dev@lists.berlios.de<br>
> Subject: Re: [Opensim-dev] OSGrid <-> UCIGrid<br>
> <br>
> Cristina Videira Lopes wrote:<br>
> > Justin Clark-Casey wrote:<br>
> >> Strong -1 on committing this code directly to core at this stage.<br>
> >><br>
> >> Charles, I strongly believe it would be better for us to see this
mature a little as an external module first, rather <br>
> >> than committing code directly to core. Please could we hold off
at least until the code has reached some level of <br>
> >> maturity, at which point we can have a discussion about what we
want to do.<br>
> >> <br>
> > +1 on Justin's -1 :-)<br>
> > There's no way I would propose the code as is today for a core patch;
<br>
> > there's a lot stuff that is still loose.<br>
> > But I hope people will want the hypergrid model enough that the <br>
> > extensions will be delivered on the same "package" as the
core, soon.<br>
> > And I hope there are volunteers from the core developers to help
bring <br>
> > this up to speed!<br>
> <br>
> Cool, thanks Cristina, glad to know that we're on the same wavelength :)<br>
> <br>
> I'm sure there will be interest from core developers - there has been
occasional conversation about looking at <br>
> alternative ways of doing things. But again, kudos for actually doing
something - rough running code is always better <br>
> than talk :)<br>
> <br>
> I'm quite keen myself but unfortunately more prosaic OpenSim server bugs
keep hitting me in the face in such a way that <br>
> I need to fix them for one reason or another.<br>
> <br>
> > <br>
> >> There is also an argument that such modules should eventually be
outside the core anyway. The OGP modules we have are <br>
> >> in there because our region infrastructure module isn't advanced
enough to make it easy to host these outside of core. <br>
> >> This is something we should address (either having some protocol
modules in or having them all out).<br>
> >> <br>
> > +1 on that too. The hypergrid extension would be even simpler than
what <br>
> > already is if only I could define externally what the comm module is.
I <br>
> > suspect OGP suffers from the same problem.<br>
> > <br>
> >> That's not to say that this isn't very interesting work,
Cristina. Does the code fit into the module structure?<br>
> >> <br>
> > Yes. As I said, the only weirdness comes because I can't spec the
comms <br>
> > module. If you change that, it will be a charm (modulo some
visibility <br>
> > changes here and there).<br>
> <br>
> Yep, apologies for not reading your previous e-mail carefully enough. When
I get a chance, I'll see if I can look at <br>
> your code and change the structure such that things are easier in this
respect (unless someone else does it first). Of <br>
> course, a patch to do such a thing is one that would be very welcome and
quickly applied too.<br>
> <br>
> >> I had thoughts along similar lines for distributed grids.<br>
> >><br>
> >>
http://justincc.wordpress.com/2008/08/15/could-there-be-a-future-without-big-grids/<br>
> >><br>
> >> but I never actually implemented anything = so fair do's to
Cristina. Also, my thoughts were to conduct everything <br>
> >> client side.<br>
> >><br>
> >> The problem does some with asset and inventory and routing this
information around. My thinking was that it would be <br>
> >> better if the client fetch this information directly rather than
via the sim, but this would require extensive (and <br>
> >> probably difficult) client changes.<br>
> >> <br>
> > A smarter client would make a lot of things a lot easier...<br>
> <br>
> God yes. Sometimes I think the fact that it is GPL'd has been a blessing
in disguise - it allows us to implement a lot <br>
> of OpenSim without accompanying time spent thinking about the client. But
it seems that things are getting to the stage <br>
> where the restrictions are as painful as they are beneficial.<br>
> <br>
> > <br>
> > _______________________________________________<br>
> > Opensim-dev mailing list<br>
> > Opensim-dev@lists.berlios.de<br>
> > https://lists.berlios.de/mailman/listinfo/opensim-dev<br>
> > <br>
> <br>
> <br>
> -- <br>
> justincc<br>
> Justin Clark-Casey<br>
> http://justincc.wordpress.com<br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> Opensim-dev@lists.berlios.de<br>
> https://lists.berlios.de/mailman/listinfo/opensim-dev<o:p></o:p></span></p>
</div>
</body>
</html>