Is there a web page/mailing list set up for this working group?  I'm 
interested in seeing what they're working on.  My understanding, though, 
was that there are some fundamental design constraints of X3D that make 
a fully shared environment exceedingly difficult.  The network node that 
you describe just bridges events between x3d browsers, which still dumps 
the entire burden of synchronization on the x3d author...

On Tue, Feb 27, 2007 at 05:44:03PM +0900, chris wrote:
> Hi everyone,
> 
> I case u haven't seen my big list posts, there is now a network working
> group for X3D aimed at putting support into X3D for
> things like routing events across network connections like you currently do
> with internal ROUTES. Of course, it will allow
> direct support for chat and game style comms internally from the Browser
> too. There is already an implementation being worked on by MediaMachines for
> their Flux Player (and other projects) - they are presenting a paper on it
> at the upcoming web3d conference in April.
> 
> Things are finally moving ahead in the web3d networking area: just think:
> ability to do low latency UDP or full featured http without having to use a
> proprietary implementation or go via some difficult external API layers. So
> if you want to support / influence the development of this part of the
> spec please join the working group.
> 
> cheers,
> 
> chris

> _______________________________________________
> vos-d mailing list
> vos-d@interreality.org
> http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d


-- 
[   Peter Amstutz  ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ]
[Lead Programmer][Interreality Project][Virtual Reality for the Internet]
[ VOS: Next Generation Internet Communication][ http://interreality.org ]
[ http://interreality.org/~tetron ][ pgpkey:  pgpkeys.mit.edu  18C21DF7 ]

Attachment: signature.asc
Description: Digital signature

_______________________________________________
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d

Reply via email to