<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:12pt"><div>Ah. Got it. The OGP notion is the Linden interop which is how the "gridnauts" got from the betagrid to an OpenSim region and to several OSGrid regions last year.<br><br>But, ... I believe those avatars that teleported from the betagrid to either the OpenSim standalone regions or the OSGrid regions were under the AgentDomain and so were "not completely, exactly", er, "handed off" to the new region. The AgentDomain was still connected to the "special client" that was being used.<br><br>Charles<br></div><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Diva Canto <diva@metaverseink.com><br><b><span
style="font-weight: bold;">To:</span></b> opensim-dev@lists.berlios.de<br><b><span style="font-weight: bold;">Sent:</span></b> Tuesday, March 3, 2009 7:50:42 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Opensim-dev] OGP/Capabilities<br></font><br>
I don't know what OGP is. I'm looking at this specific document, and
it's as generic as a document can be. Specifically, it doesn't say
anything about how to use the basic protocols HTTP+REST+CAPs. The
different uses will produce quite different systems, I think.<br>
<br>
<br>
Charles Krinke wrote:
<blockquote type="cite">
<div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;">
<div>If I recall correctly, and I might be wrong, but the
conversation I had with the lindens about OGP had them focused on their
AgentDomain. Sort of a "super grid server" if you will. When quizzed
about a full handoff, they said "we arent working on that".<br>
<br>
So, my impression about OGP is it extends the linden grid, but is only
half of an interop solution.<br>
<br>
Charles<br>
</div>
<div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;"><br>
<div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font size="2" face="Tahoma">
<hr size="1"><b><span style="font-weight: bold;">From:</span></b>
Diva Canto <a rel="nofollow" class="moz-txt-link-rfc2396E" ymailto="mailto:diva@metaverseink.com" target="_blank" href="mailto:diva@metaverseink.com"><diva@metaverseink.com></a><br>
<b><span style="font-weight: bold;">To:</span></b>
<a rel="nofollow" class="moz-txt-link-abbreviated" ymailto="mailto:opensim-dev@lists.berlios.de" target="_blank" href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
<b><span style="font-weight: bold;">Sent:</span></b> Tuesday, March
3, 2009 7:31:32 PM<br>
<b><span style="font-weight: bold;">Subject:</span></b> [Opensim-dev]
OGP/Capabilities<br>
</font><br>
Finally Linden Lab produced an interesting document:<br>
<a rel="nofollow" target="_blank" href="http://www.ietf.org/internet-drafts/draft-lentczner-ogp-base-00.txt">http://www.ietf.org/internet-drafts/draft-lentczner-ogp-base-00.txt</a><br>
<br>
I think capabilities are the right concept here, and I'm pleased to see
<br>
them taking center stage in that document. In particular the hint at <br>
inventory-related capabilities, which will allow secure inventory
access.<br>
<br>
I'm not sure I buy into some of the details, but the basic combination <br>
HTTP+REST+Capabilities --> +1.<br>
<br>
The Event Queue...well... It sucks. I think we need to look at <br>
alternatives for posting things to the client. I can't believe there <br>
aren't any; I think there are, but maybe they all come down to this, <br>
event queues on the server-side, whatever their form.<br>
<br>
If there are no better alternatives, then we need at least to rethink <br>
what the EQ is all about. If the EQ CAP is not given to the regions,
but <br>
stays within the user's home system, that might work. Also, if there <br>
would be several different *types* of Event Queues that might work well
<br>
too; so for example, we might give the social-net-related EQ CAP <br>
(groups, IM, etc) to the social net component without compromising
agent <br>
transfers. The more I think about this, the more I'm convinced that <br>
regions have no business in agent transfer activities, other than <br>
negotiating the capabilities when agents come.<br>
<br>
I really like that document, I must say, but it's strength is also its <br>
weakness. It's just about the basic levels. It says nothing about how <br>
those things are driven higher up.<br>
<br>
Crista<br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a rel="nofollow" ymailto="mailto:Opensim-dev@lists.berlios.de" target="_blank" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a rel="nofollow" target="_blank" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div>
</div>
</div>
<pre><hr size="4" width="90%">
_______________________________________________
Opensim-dev mailing list
<a rel="nofollow" class="moz-txt-link-abbreviated" ymailto="mailto:Opensim-dev@lists.berlios.de" target="_blank" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a rel="nofollow" class="moz-txt-link-freetext" target="_blank" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</pre>
</blockquote>
<br>
</div></div></div></body></html>