As far as HyperGrid and when it is ready for prime time I do not think there is anyone who could speak to that better than Cristina. Kyle
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Cristina Videira Lopes Sent: Wednesday, June 03, 2009 3:38 PM To: [email protected] Subject: [Opensim-dev] OGPX and IETF-ing things Inifinity sent me a very nice private message, which, because it was private, I'm not going to forward here. But the bottom line of his nice message could use some public discussion. Essentially Infinity is suggesting that we move towards getting the Hypergrid work into the IETF, through this newly created OGPX working group. Personally, I think this is all premature. IETF-ing the Hypergrid is premature for different reasons than IETF-ing OGP is premature. The Hypergrid is not really ready for prime time until we have the Hypergrid2 in place, with its security model to protect users from malicious simulators. OGP is not ready for prime time because no one has seen it yet, at least not any reasonably complete implementation of it. The right thing to do, I think, is to first have implementations of both OGP and the Hypergrid2 in OpenSim. Once that is in place, we can all see the similarities and differences, and try to standardize the similar pieces. Alternatively, we can try to work together towards one single interop protocol, but honestly I think that's not going to happen, simply because there is space for many (not just 2, but 3 or 4) What I suspect will happen is that OGP and the Hypergrid will have several pieces that are very much in sync, with small details that are different, and then they will have a few really important pieces that are substantially different. Things like posting/retrieving agents to/from regions, for example, we already converged to using REST; inventory access, we already converged to using capability URLs, etc. Small details such as the format of the data on the wire are different, but that doesn't really matter as long as we agree that the Content-type can be set to different things. The thing that will be substantially different is the issue of authority: what component has authority to do what. In OGP regions are still the ones doing agent transfers, therefore implying a trust relation between interacting grids that must be established in some non-technical manner (i.e. the receiving region trusts that the sending region is not stealing the user's identity). In the Hypergrid, agent transfers between non-trusting regions are done on the client side, so that the identity of the user can always be verified, there is no region in the middle acting on behalf of anyone. So, that's the main difference, as far as I understand OGP. The Hypergrid2 is in place through a proof-of-concept prototype client (Grider) and a couple of small but horrible hacks in OpenSim. OGP implementations don't exist yet, or they are not available to us which is the same. I think there's a lot of work to do before we go and propose any of this as standards. But I thought I'd bring this up for discussion. Maybe other people aren't as strict on working implementations as I am. Crista _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
BEGIN:VCARD VERSION:2.1 X-MS-SIGNATURE:YES N;LANGUAGE=en-us:Gomboy;Kyle FN:Kyle Gomboy ORG:ReactionGrid TITLE:CEO/Developer TEL;WORK;VOICE:(407) 992-8284 ADR;WORK:;;1401 Parkland Blvd.;Ft. Pierce;FL;34982;United States of America LABEL;WORK;ENCODING=QUOTED-PRINTABLE:1401 Parkland Blvd.=0D=0A= Ft. Pierce FL=0D=0A= 34982 X-MS-OL-DEFAULT-POSTAL-ADDRESS:1 URL;WORK:http://www.reactiongrid.com EMAIL;PREF;INTERNET:[email protected] X-MS-OL-DESIGN;CHARSET=utf-8:<card xmlns="http://schemas.microsoft.com/office/outlook/12/electronicbusinesscards"; ver="1.0" layout="left" bgcolor="ffffff"><img xmlns="" align="fit" area="16" use="cardpicture"/><fld xmlns="" prop="name" align="left" dir="ltr" style="b" color="000000" size="10"/><fld xmlns="" prop="org" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="title" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="telwork" align="left" dir="ltr" color="000000" size="8"><label align="right" color="626262">Work</label></fld><fld xmlns="" prop="email" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="addrwork" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="webwork" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/></card> REV:20090330T190050Z END:VCARD
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
