Re: [vwrap] Consensus? What exactly should be in the protocol

Cristina Videira Lopes <lopes@ics.uci.edu> Wed, 22 September 2010 18:59 UTC

Return-Path: <lopes@ics.uci.edu>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 410483A6B35; Wed, 22 Sep 2010 11:59:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.354
X-Spam-Level:
X-Spam-Status: No, score=-2.354 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599]
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 d78RbSCag1ei; Wed, 22 Sep 2010 11:59:43 -0700 (PDT)
Received: from david-tennant-v0.ics.uci.edu (david-tennant-v0.ics.uci.edu [128.195.1.174]) by core3.amsl.com (Postfix) with ESMTP id 58BA93A6A69; Wed, 22 Sep 2010 11:59:43 -0700 (PDT)
Received: from [169.234.251.90] (barbara-wright.ics.uci.edu [128.195.1.137]) (authenticated bits=0) by david-tennant-v0.ics.uci.edu (8.13.8/8.13.8) with ESMTP id o8MJ04n7022617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Sep 2010 12:00:05 -0700
Message-ID: <4C9A5226.2080601@ics.uci.edu>
Date: Wed, 22 Sep 2010 11:59:50 -0700
From: Cristina Videira Lopes <lopes@ics.uci.edu>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: lopes@ics.uci.edu
References: <AANLkTinxpGRZ9PEWQx=KvaBNGBba4Z+P+SaP4N80VGV1@mail.gmail.com> <E2109887-F5B2-4742-B4F7-1C4655A2DD8B@ics.uci.edu> <62BFE5680C037E4DA0B0A08946C0933D012670D0C9@rrsmsx506.amr.corp.intel.com> <4C9A070B.3070202@hp.com> <AANLkTinVX6Uo2S+7ocdTiVfiTFa9wxM=x1Cncyi5ij86@mail.gmail.com> <4C9A17FC.9090308@ics.uci.edu> <OF98CA2B26.9D4927A8-ON852577A6.00572945-852577A6.0060FB5D@us.ibm.com> <4C9A45FC.6030709@ics.uci.edu>
In-Reply-To: <4C9A45FC.6030709@ics.uci.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ICS-MailScanner-Information: Please send mail to helpdesk@ics.uci.edu or more information
X-ICS-MailScanner-ID: o8MJ04n7022617
X-ICS-MailScanner: Found to be clean
X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44)
X-ICS-MailScanner-From: lopes@ics.uci.edu
Cc: vwrap@ietf.org, vwrap-bounces@ietf.org
Subject: Re: [vwrap] Consensus? What exactly should be in the protocol
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: lopes@ics.uci.edu
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2010 18:59:44 -0000

Cristina Videira Lopes wrote:
> You can dictate that. But then this will be completely irrelevant in a 
> couple of years when WebGL is actually usable or when Google finishes 
> their virtual machine for running safe native code on browsers.
...or when server-side streaming goes mainstream, and being in a virtual 
world is as simple as running a video player plus a few 
JavaScript/native back channels to the server.

First point is: according to the Web principles, each web application 
controls 100% what and how the client gets via this really powerful 
concept of hypermedia. It is unlikely that the world is going to adopt a 
standard that forces implementers to take several steps back on this 
kind of autonomy. The diversity is what gives service providers an edge.

The second point is: when we have all that variety of viewer 
implementations that are all equally accepted by the web browser, we are 
still to cope with portability of user agent simulation state between 
those worlds -- and that's the bottom line for interoperability of 
virtual worlds on the Web. I'm interested in this, because it's much 
more foundational than the variety of virtual world implementation options.