On 2/28/07, Peter Amstutz <[EMAIL PROTECTED]> wrote:
Is there a web page/mailing list set up for this working group? I'm
there is a link to working groups at: http://www.web3d.org/x3d/workgroups/ which has links on how to join underneath. 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
No real constraints - it is general networking capability and routing between Browsers is only one of the applications. You could do chat with an XMPP chat client, communicate with a server thru a port, send binary encoded bytes to / from anything. It is designed to generate events in/out of the sensor node but there is complete flexibility as to what you map to what fields and it allows for either sending X3D encoded stuff or a protocol of your own making. You could, for example, send packets containing two integers and have them routed to an MFInt32. more details here: http://planet-earth.org/x3d/networkSensor.html and: http://planet-earth.org/x3d/networkSensorProposal.html http://planet-earth.org/x3d/UIUseCase.html http://planet-earth.org/x3d/ExampleNetworkSensor.html The SWAMP protocol being implemented by MediaMachines is specific to using the X3D scenegraph model - which has some advantages - but that would be separate from, say, a chat channel which could be running on another port. hope that is clear enough, chris 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 > [email protected] > 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 ] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFF5ElqaeHUyhjCHfcRAhJzAJ43YKsgrZzAtKgne1NRKnwzXB8JIACfTIiV mQ8vOVeXkP4002UnS6RCFQs= =6njc -----END PGP SIGNATURE----- _______________________________________________ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
_______________________________________________ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
