Re: [vwrap] one question

[Crista Lopes <[e-mail]>]

On 9/24/2010 2:23 PM, Hurliman, John wrote:
>
> In this example, you are defining an interop mechanism that relies on fetching a Javascript blob and executing it to be able to fetch content from another virtual world.
I was not thinking about the JavaScript program accessing the other 
world's assets directly, but there you go: you thought about it, so you 
might do it, while I might not.

> That's one possible way of doing virtual world interop, but unfortunately it rules out a large category of clients by using Javascript execution *as your interop mechanism*.
I'm not. The interop should be world-to-world. The JavaScript program is 
just a renderer and UI.

> You could also do OpenID authentication that way, by just downloading blobs of Javascript that know how to present an authentication UI, phone home, and do their work. Maybe this is how some worlds will interoperate, but it's not VWRAP and it's not in scope.
>
>    

ok. It's good to know that this is out of scope!


>> Next step: dahlia is developing a Unity3D browser plugin for OpenSim. I want
>> to go from your world to dhalia's world. So some UI happens, and I go to her
>> world. I need to download the Unity3D web plugin, if I don't have it already,
>> and once is installed I also get the content in whichever way dahlia's code
>> makes them come the way of my browser. Her world should know who I am,
>> and how to get my assets.
>>
>>      
> This is where the need for a VWRAP protocol comes in; where you can no longer rely on the "execute some opaque Javascript to perform interop" method to communicate identity, assets, and a teleport handshake between two different platforms. Her world should definitely know who you are and how to get your assets, and the way it knows those things is by speaking the VWRAP protocol.
>
>    
Well, *some* interop protocol, I agree. I'm not convinced that VWRAP, as 
described in the documents, is needed.


>> These are all independently-operated worlds with radically different ways of
>> placing the assets in my machine. And yet I ought to be able to visit them all
>> while they know who I am and how to render my avatar.
>>
>> Is this clear?
>>
>>      
> Each world has its own protocols and those are out of scope of VWRAP, yet you ought to be able to visit all these different worlds and move identity and assets and presence between them, which is where a precisely defined protocol like VWRAP comes in and says you form a URL just like this and put these exact bits on the wire and you get back this response to complete the exchange. If we're in agreement on that statement then what you said is clear.
>
>    

Great. Now can you please explain to me why this matters for interop:
http://tools.ietf.org/html/draft-ietf-vwrap-authentication-00
Not just the title, but the actual content of that draft.