We're testing remote 3D rendering over WebRTC. We render the 3D world in the cloud. Video and controls go over a WebRTC-connection. I wrote a simple nodejs websocket server to handle the signaling.<p>It has been a quite wonderful experience despite the tech being somewhat experimental. Google Chrome offers excellent tools (chrome://webrtc-internals/ & chrome://webrtc-logs/).<p>First I wrote the client and a mock server to work in the browser while a colleague started implementing webrtc to work in the renderer with the PeerConnectionpp-lib. Debuggin was awesome, when you had a working mock renderer in the browser.<p>All the bugs I encountered we're my own and I found all the answers I needed in the dev API doc:
<a href="http://dev.w3.org/2011/webrtc/editor/webrtc.html" rel="nofollow">http://dev.w3.org/2011/webrtc/editor/webrtc.html</a>