Re: [vwrap] Some thoughts on Josh's Linden Lab Legacy Protocol discussion

David W Levine <dwl@us.ibm.com> Wed, 28 April 2010 16:14 UTC

Return-Path: <dwl@us.ibm.com>
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 2837C3A6B54 for <vwrap@core3.amsl.com>; Wed, 28 Apr 2010 09:14:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.498
X-Spam-Level:
X-Spam-Status: No, score=-3.498 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 cbs0qz-bO+j7 for <vwrap@core3.amsl.com>; Wed, 28 Apr 2010 09:14:28 -0700 (PDT)
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.143]) by core3.amsl.com (Postfix) with ESMTP id B9E443A6B21 for <vwrap@ietf.org>; Wed, 28 Apr 2010 09:14:25 -0700 (PDT)
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by e3.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id o3SG1k2j032080 for <vwrap@ietf.org>; Wed, 28 Apr 2010 12:01:46 -0400
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o3SGECCY165882 for <vwrap@ietf.org>; Wed, 28 Apr 2010 12:14:12 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id o3SGEBAp016034 for <vwrap@ietf.org>; Wed, 28 Apr 2010 13:14:11 -0300
Received: from d01ml605.pok.ibm.com (d01ml605.pok.ibm.com [9.56.227.91]) by d01av03.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVin) with ESMTP id o3SGEBDC016028; Wed, 28 Apr 2010 13:14:11 -0300
In-Reply-To: <5FD507B0-6D81-4945-9D8A-DE3FF81C7507@intel.com>
References: <OF12BB21F8.3FAB95C0-ON85257712.0076D115-85257712.00773210@us.ibm.com> <5FD507B0-6D81-4945-9D8A-DE3FF81C7507@intel.com>
To: "Hurliman, John" <john.hurliman@intel.com>
MIME-Version: 1.0
X-KeepSent: 3E7A4FA5:8A889E67-85257713:0056A958; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009
Message-ID: <OF3E7A4FA5.8A889E67-ON85257713.0056A958-85257713.005930A8@us.ibm.com>
From: David W Levine <dwl@us.ibm.com>
Date: Wed, 28 Apr 2010 12:14:11 -0400
X-MIMETrack: Serialize by Router on D01ML605/01/M/IBM(Release 8.5.1HF41 | October 22, 2009) at 04/28/2010 12:14:11, Serialize complete at 04/28/2010 12:14:11
Content-Type: multipart/alternative; boundary="=_alternative 005930A885257713_="
Cc: "vwrap@ietf.org" <vwrap@ietf.org>
Subject: Re: [vwrap] Some thoughts on Josh's Linden Lab Legacy Protocol discussion
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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, 28 Apr 2010 16:14:29 -0000

"Hurliman, John" <john.hurliman@intel.com> wrote on 04/28/2010 11:39:06 
AM:

> [image removed] 
> 
> Re: [vwrap] Some thoughts on Josh's Linden Lab Legacy Protocol 
discussion
> 
> Hurliman, John 
> 
> to:
> 
> David W Levine
> 
> 04/28/2010 11:40 AM
> 
> Cc:
> 
> "vwrap@ietf.org"
> 
> Does the method for exposing an API need to be different from the 
> method that exposes a user interface?
> 
> John
> 

I've been giving that exact question some serious thought. One simple
answer is to say, as we often do, "Content Negotiation Saves the day!"
If you want the programatic api, ask for application/xml, if you want 
something to present to the user, ask for text/html. If one wants to be
stronger, make the mime types more explicit. (I'm not thrilled with this
because if we can reuse existing, obvious mime types, I tend to think
its much better) 

But.. there are at least two things which make me go "maybe not." Part
one is, well, contextual. Do we expose things primarily as part of the
visual client centric scenegraph? If we tie things to closely to be
"logged in" to a region and having a client, then we end up making it
much harder for applications (and for that matter clients) which are
substantially different than the current client. We get a lot of power
by saying "This service/ui/api" is associated with "this portion of the
scenegraph." in terms of the immersive user experience. But.. the same
power gets in the way of web service like integration where one might well
want to simply expose a URI that lets you directly manipulate things in
a portion of the world. 

My current rough thinking is that if we do things correctly, we can expose
the same API via both "web external" facing discovery and 
"scenegraph internal" facing discovery. If we let the UI/API be chosen
by content negotiation, we may be done. (Tho, I'm not at all user exposing
a UI will help much, as you'll likely not have enough context to do 
anything
useful with it, but.. I can imagine clients which will) 

As I said. Very much partly baked thinking at the moment, ripe for 
discussion.

- David
~ Zha


> On Apr 27, 2010, at 2:42 PM, "David W Levine" <dwl@us.ibm.com<
> mailto:dwl@us.ibm.com>> wrote:
> 
> 
> As always, food for thought, probably partly baked.
> 
> Josh Linden's presentation on the Linden Legacy Protocol
[snip]