Re: [ogpx] A blog post from the HTML5/Websocket wars worth reading
Joshua Bell <josh@lindenlab.com> Fri, 19 February 2010 17:29 UTC
Return-Path: <josh@lindenlab.com>
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 D325D3A7D4B; Fri, 19 Feb 2010 09:29:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level:
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 ARYA9XvE9O5T; Fri, 19 Feb 2010 09:29:35 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 38B8E3A7EBF; Fri, 19 Feb 2010 09:29:35 -0800 (PST)
Received: by wwb31 with SMTP id 31so27396wwb.31 for <multiple recipients>; Fri, 19 Feb 2010 09:31:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.90.130 with SMTP id e2mr767089wef.210.1266600679083; Fri, 19 Feb 2010 09:31:19 -0800 (PST)
In-Reply-To: <OF770EB04C.B05AF5F9-ON852576CF.005262EB-852576CF.005A587A@us.ibm.com>
References: <OFE468F9B5.25216572-ON852576CD.0053ADC1-852576CD.0053E11E@us.ibm.com> <382d73da1002170836x3c689a89ve5e62a67e6173bdc@mail.gmail.com> <OF7F0480B9.5C99B16B-ON852576CD.00623CB9-852576CD.006335DE@us.ibm.com> <e0b04bba1002180129if2eeabv5eb7f7db76bfaf1d@mail.gmail.com> <6c9fcc2a1002180918p2bf40959v32a1163848c76717@mail.gmail.com> <20100219141252.GA16509@alinoe.com> <OF770EB04C.B05AF5F9-ON852576CF.005262EB-852576CF.005A587A@us.ibm.com>
Date: Fri, 19 Feb 2010 09:31:18 -0800
Message-ID: <f72742de1002190931r4255573ewe847ec646f19b065@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: David W Levine <dwl@us.ibm.com>
Content-Type: multipart/alternative; boundary="0016e6db29798c8d7b047ff7736d"
Cc: ogpx-bounces@ietf.org, barryleiba@computer.org, ogpx@ietf.org
Subject: Re: [ogpx] A blog post from the HTML5/Websocket wars worth reading
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: Fri, 19 Feb 2010 17:29:36 -0000
+1 As we have no exemplars of a VWRAP compatible system at the moment, so it's hard to point at one and say "like that!" Hence the use of SL, as a guiding example of the abstract theory, if not (currently!) the practice, as outlined by David's mail. But yes, we should absolutely be saying "VWRAP-compatible" rather than "SL-like" when we're discussing anything formally, and point at the Intro draft (which everyone has read and likes, yes?) to clarify what that means. On Fri, Feb 19, 2010 at 8:26 AM, David W Levine <dwl@us.ibm.com> wrote: > > At some level, it's a tautology. Since the VWRAP spec, not Second Life, is > going to define VWRAP compatibility, it can't be any other way. > > At the same time, the path from AWG->MMOX->OGPX->VWRAP is all about finding > a subset of possible virtual worlds which is big > enough to be interesting, and small enough to be manageable. "Second Life > Like" has been a convenient short hand to scope the > problem. What does it mean? I believe its Roughly the following: (Glancing > at our charter) > > - Avatars representing users > - Named Persistent areas of virtual space (Regions) > - Region centric state management (you can get state from the > services facaded by a URI) > - Services delivered over web interfaces > - Policies > > That's certainly "Second Life like" its certainly "OpenSim Like." > > I fully expect that part of the challenge going forward is going to be > providing sufficient markup > so that world which fit within the broad umbrella of VWRAP, but differ in > significant ways can signal > those differences, allowing sane interoperation. I also fully expect some > mighty odd things to happen > when someone teleports from a grid with one physics to a grid with a > different physics model unless > the client, and the protocols signal properly. But.. I also think if we are > at that point, we're winning, not losing. > > - David > ~ Zha > > > > > > From: > Carlo Wood <carlo@alinoe.com> > To: barryleiba@computer.org Cc: ogpx@ietf.org Date: 02/19/2010 09:13 AM > Subject: > Re: [ogpx] A blog post from the HTML5/Websocket wars worth reading > Sent by: ogpx-bounces@ietf.org > ------------------------------ > > > > On Thu, Feb 18, 2010 at 12:18:42PM -0500, Barry Leiba wrote: > > > VWRAP is not a protocol to enshrine a particular form of world, but a > > > protocol to define a particular form of interop. We often make the > mistake > > > of referring to "SL-like worlds" in these discussions, when what we > really > > > mean is "VWRAP-compatible worlds". There is certainly no need to be > SL-like > > > nor even SL-compatible when using VWRAP. For example, VWRAP will > > > undoubtedly be used by leading-edge worlds with services and assets > that > > > Linden Lab chooses not to handle, as a business choice. > > > > > > Therefore "SL-like" is a very incorrect phrase here. We mean > > > VWRAP-compatible. > > > > What she said. > > > > Barry > > Agreed. SL should be VWRAP compatible, but there is no need > for another world that uses VWRAP to really be anything like SL. > > -- > Carlo Wood <carlo@alinoe.com> > _______________________________________________ > ogpx mailing list > ogpx@ietf.org > https://www.ietf.org/mailman/listinfo/ogpx > > > > _______________________________________________ > ogpx mailing list > ogpx@ietf.org > https://www.ietf.org/mailman/listinfo/ogpx > >
- [ogpx] A blog post from the HTML5/Websocket wars … David W Levine
- Re: [ogpx] A blog post from the HTML5/Websocket w… Kari Lippert
- Re: [ogpx] A blog post from the HTML5/Websocket w… David W Levine
- Re: [ogpx] A blog post from the HTML5/Websocket w… Morgaine
- Re: [ogpx] A blog post from the HTML5/Websocket w… Barry Leiba
- Re: [ogpx] A blog post from the HTML5/Websocket w… Carlo Wood
- Re: [ogpx] A blog post from the HTML5/Websocket w… Meadhbh Hamrick
- Re: [ogpx] A blog post from the HTML5/Websocket w… David W Levine
- Re: [ogpx] A blog post from the HTML5/Websocket w… Joshua Bell
- Re: [ogpx] A blog post from the HTML5/Websocket w… Carlo Wood
- [ogpx] Updated deployment and trust draft posted David W Levine
- Re: [ogpx] Updated deployment and trust draft pos… Infinity Linden (Meadhbh Hamrick)
- Re: [ogpx] Updated deployment and trust draft pos… Lawson English
- Re: [ogpx] Updated deployment and trust draft pos… Morgaine
- Re: [ogpx] Updated deployment and trust draft pos… Carlo Wood
- Re: [ogpx] Updated deployment and trust draft pos… Meadhbh Hamrick