Re: [vwrap] one question

I'll respond with my own perspective and goal. If we standardize the initial set of features I outlined in my previous e-mail, that web browser client would interoperate with any virtual world that supported the particular state synchronization protocol it uses (which I imagine will be WebSocket+JSON based, but VWRAP would not care about nor try to intrude on). One asset server could serve assets to a variety of heterogeneous VWs, one identity server could work across a variety of VWs, but clients would only be able to connect to worlds that they had state sync protocol support for.

I'm definitely open to the possibility of standardizing more things and moving beyond that level of interop, but that's my goal for step one.

John

> -----Original Message-----
> From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf
> Of Cristina Videira Lopes
> Sent: Wednesday, September 22, 2010 6:48 PM
> To: vwrap@ietf.org
> Subject: [vwrap] one question
> 
> Let me summarize my main puzzlement with the drafts, and with some of
> the things stated here, with one very simple yes/no question that,
> hopefully, the group will get to a consensus in no time:
> 
> I have a student starting to work on a JavaScript+HTML5 viewer for
> brain-dead-simple, multi-user, OpenSimulator-served scenes. I can do
> that very easily with OpenSim, since the client protocol is a plugin.
> Is
> VWRAP set up to develop protocols for interoperability between virtual
> worlds that, like these ones, use the web browser as the client?
> a) Yes
> b) No
> 
> People's answers?
> 
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap