Re: [ogpx] Teleports and protocol resilience
Charles Krinke <cfk@pacbell.net> Tue, 13 October 2009 17:09 UTC
Return-Path: <cfk@pacbell.net>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id E60AA3A6967 for <ogpx@core3.amsl.com>;
Tue, 13 Oct 2009 10:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id npvttNJHJ9cj for
<ogpx@core3.amsl.com>; Tue, 13 Oct 2009 10:09:13 -0700 (PDT)
Received: from web82603.mail.mud.yahoo.com (web82603.mail.mud.yahoo.com
[68.142.201.120]) by core3.amsl.com (Postfix) with SMTP id EAD3F3A67DD for
<ogpx@ietf.org>; Tue, 13 Oct 2009 10:09:12 -0700 (PDT)
Received: (qmail 28038 invoked by uid 60001); 13 Oct 2009 17:09:11 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net;
h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type;
b=gCcQUpDW6SVubReh184b39JB6BOe4UjCOXFm8wVeozlNYryTq095L3to1j5ZakkoxEy2gQy5TjnhLFSbpQn+xYxB7b5/cmMVe9IZ67FEyxNyP2guZHQFEYIzlhlAFw/MQvO+TLB9gIUSzcpucSZrxuNJep2f2/uZCbEKNiBPiZM=;
Message-ID: <929772.26592.qm@web82603.mail.mud.yahoo.com>
X-YMail-OSG: W4qyONoVM1nX6YJUT7FnoHyQl8FAduGAY1rADpwkpdKgenUVYtP21sb4GSHvIJOhtA_HDE3OWqa9cnMbqHf6LhT4NuaCtDtvWA8Ct_IzqE.iDO8EUAucD3XNaxMGsqyjPngHCkscqFpqmNaQ8YX.UnWplrQAg.cMUAaOxxwKnCi5MM6wGasf8D4c0.3_z01S_cVm.IrRw23fG_DcnYFqiIc2E66nmVZ5nqiQ6P4N3XaCCy3fU6_9gBdVMFzcSIm85MQJGd6NSRn6HpBrVhZRI.LBk.V3crTXE4q4ck8mDWCMgnXF4TIzbK6EPO2AAgJOFRWh3tYwMYynnTzGHOmgHNKPHFp2LdFwWTmZyfQNgd9ItnaYP7nNtpA4gM_Wi4g47F1yfoeU6EngPNm7IBXagkAawe0RbA1Tq2wo9wJKLD3t
Received: from [216.156.179.114] by web82603.mail.mud.yahoo.com via HTTP;
Tue, 13 Oct 2009 10:09:10 PDT
X-Mailer: YahooMailRC/182.10 YahooMailWebService/0.7.347.3
References: <e0b04bba0910122213n66886b92x57446ad84def466f@mail.gmail.com>
<f72742de0910130853y2e14a37bkef366f7ddcbf1f63@mail.gmail.com>
<1255452933.4156.21.camel@mdickson-linux.local>
Date: Tue, 13 Oct 2009 10:09:10 -0700 (PDT)
From: Charles Krinke <cfk@pacbell.net>
To: Mike Dickson <mike.dickson@hp.com>, Joshua Bell <josh@lindenlab.com>
In-Reply-To: <1255452933.4156.21.camel@mdickson-linux.local>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-248207747-1255453750=:26592"
Cc: "ogpx@ietf.org" <ogpx@ietf.org>
Subject: Re: [ogpx] Teleports and protocol resilience
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>,
<mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>,
<mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2009 17:09:14 -0000
Good point, Mike. I suspect the answer is going to be in how the protocol handles 'graceful' failure for teleports when the 'toRegion' has one or more settings that are different then the 'fromRegion'. Charles ________________________________ From: Mike Dickson <mike.dickson@hp.com> To: Joshua Bell <josh@lindenlab.com> Cc: "ogpx@ietf.org" <ogpx@ietf.org> Sent: Tuesday, October 13, 2009 9:55:33 AM Subject: Re: [ogpx] Teleports and protocol resilience On Tue, 2009-10-13 at 15:53 +0000, Joshua Bell wrote: > One of the reasons that this fails today is that the origin RD > maintains some amount of agent state (e.g. script state for > attachments). For a sim-to-sim handoff, the origin RD must > successfully transmit information either to the AD or the destination > RD (or both), otherwise the user experience is poor (information is > lost). Note that this needs to happen during a simple logoff/login as > well. It seems to me that agent state in the AD should have ACID-ish > characteristics, including the agent's current location. The scripting comment is interesting re: interoperability also. What does that imply if I'm going from an OpenSim instance for example which has additional scripting functions enabled that a SL region might not support. How does the destination region determine it can run the scripts in attachments and that its safe to do so? Mike _______________________________________________ ogpx mailing list ogpx@ietf.org https://www.ietf.org/mailman/listinfo/ogpx
- [ogpx] Teleports and protocol resilience Morgaine
- Re: [ogpx] Teleports and protocol resilience Kari Lippert
- Re: [ogpx] Teleports and protocol resilience Infinity Linden (Meadhbh Hamrick)
- Re: [ogpx] Teleports and protocol resilience Joshua Bell
- Re: [ogpx] Teleports and protocol resilience David W Levine
- Re: [ogpx] Teleports and protocol resilience Meadhbh Hamrick
- Re: [ogpx] Teleports and protocol resilience Mike Dickson
- Re: [ogpx] Teleports and protocol resilience Charles Krinke
- Re: [ogpx] Teleports and protocol resilience Joshua Bell
- Re: [ogpx] Teleports and protocol resilience Vaughn Deluca
- Re: [ogpx] Teleports and protocol resilience Joshua Bell
- Re: [ogpx] Teleports and protocol resilience Vaughn Deluca
- Re: [ogpx] Teleports and protocol resilience Meadhbh Hamrick
- Re: [ogpx] Teleports and protocol resilience Dan Olivares
- Re: [ogpx] Teleports and protocol resilience Meadhbh Hamrick
- Re: [ogpx] Teleports and protocol resilience Vaughn Deluca
- Re: [ogpx] Teleports and protocol resilience Morgaine
- Re: [ogpx] Teleports and protocol resilience David W Levine
- Re: [ogpx] Teleports and protocol resilience Morgaine
- Re: [ogpx] Teleports and protocol resilience Lawson English
- Re: [ogpx] Teleports and protocol resilience Morgaine
- Re: [ogpx] Teleports and protocol resilience Vaughn Deluca
- Re: [ogpx] Teleports and protocol resilience Morgaine
- Re: [ogpx] Teleports and protocol resilience Carlo Wood