<br>DIS and XMPP are examples of application protocols that the network sensor was designed to support at a portable node level - i.e. without requiring a proprietary java or C implementation. Perhaps there are alternative ways to do this in portable X3D code, I don't know.<br>
<br>"Perhaps more effort needs to be put into an easy to use, standard
dynamic scenegraph that is implemented across all browsers, and the
question about MU protocols will go away." - only if it also addresses peer to peer and client-server communications as well.<br><br>Anyway, I agree with your summary statement.<br><br>cheers,<br><br>chris<br><br><div class="gmail_quote">
On 5 May 2010 15:07, John Carlson <span dir="ltr"><<a href="mailto:john.carlson3@sbcglobal.net">john.carlson3@sbcglobal.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I am thinking that people who are interested in graphics and those that are interested in MU networking are different folks. Here we have a bunch of graphics weenies who have essentially bought into the DOM, and forgot about GLX/XGL or whatever the networked OpenGL was (perhaps it was too slow or not scalable?). Now WebGL is taking over the role of GLX/XGL, and the DOM folks are trying desperately to layer on top of it. Hence X3DOM. Perhaps when people think about browsers, they think in terms of a person accessing a server, and they don't see peer to peer interaction. They also think about how slow it is to go through a server. Guess what? Google is already doing multiuser stuff from the web with XMPP (google wave). And guess what else? NetBeans can provide for simultaneous editing of X3D with XMPP (X3D Edit). If you want a MU protocol, why not or why not choose DIS, Open-DIS or DIS-XML (encoded with EXI)? Note that I have not programmed to XMPP or DIS. I have tried to create unsuccessfully, an X3D scene to add arcs and nodes to an X3D scene (yes, I've done it with JOGL). Perhaps more effort needs to be put into an easy to use, standard dynamic scenegraph that is implemented across all browsers, and the question about MU protocols will go away. Yes, I realize this dynamism is verboten, but it's why people program in WebGL, JOGL, OpenGL instead of X3D or VRML--It looks like X3DOM will provide a way to add and delete nodes in HTML5. Is there appreciable impact on performance by making a dynamic scene? What about IE?<br>
<br>
In summary, get a standard dynamic scenegraph working the same in all browsers, and your MU problems will go away.<br>
<br>
Use the GPU Luke.<br>
<br>
For beginners DOM = retained/structured mode<br>
WebGL = immediate mode<br>
Two styles of programming graphics.<br>
<div><div></div><div class="h5">_______________________________________________<br>
X3D-Public mailing list<br>
<a href="mailto:X3D-Public@web3d.org">X3D-Public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.vrshed.com">http://www.vrshed.com</a><br>There be greater truth at the centre: <a href="http://www.floatingorigin.com">http://www.floatingorigin.com</a><br>
<br><br>