Re: [vwrap] Technical basis for VW client in a web browser?

[peter host <[e-mail]>]

> There is nothing that VW protocols can do to alleviate these shortcomings of
> the browser platform, because virtual worlds don't work like websites.  The
> in-world objects and the avatars are highly stateful and persistent, the
> users in a region all see each other, interoperating objects travel between
> worlds in what would be Web cross-site anathema, and there is nothing
> remotely like transparent region crossing in Web apps.  Really we're talking
> about chalk and cheese here.

hmmm... you might want to take a look at node.js' implementation of socketio.
It's already there and already working.
I am personally working for my current clients on a project which
links websites virtually (via a javascript client)
showing you what your 'friends' are doing, on the website, in real
time. It's 'co-surfing'. Mouse movement, clicks & all. And there's
quite a lot of data going back and forth. Our major limitation is the
lattency of TCP.

NB : the term web apps might be misleading. The sort of apps
websockets make feasible
 don't really care about the 'document' web, they are endpoints for
octet streams, and 'web' servers are just only proxies to lower-level
interfaces (say a ROBUST server, a datastore, whatever)


> SGML's crown was usurped by HTML as a simpler format that worked better in
> the online markup space.  But VWs are already an online space, a newer one
> than the Web, and Web browsers don't work better in this new space at all.

Good point.