On 12/4/11 3:06 AM, Eric Appleman wrote: > Basically, how are cursors and keyboard input dealt with on both the > server and client end.
They aren't. VirtualGL relies on X11 to do all of that. VirtualGL only takes care of transmitting the 3D images. > For windows, how are window properties translated between both? How is > the client window isolated from the server's root window? Let's back up, because I think there is a fundamental misunderstanding of how VGL works. There is the "3D X server", which is the X server that is running on the server machine, which has 3D hardware attached, and which is used to access said 3D hardware. Then there is the "2D X server", which is the X server that receives the final output of the application, and with which you interact to control the application. The 2D X server can either be a "real" X server running on the client machine, in which case you use the VGL Transport to send the 3D images from the server machine over to it-- or the 2D X server can be an X proxy, such as VNC, in which case the 3D images are sent via X11 calls. In either case, VirtualGL does not deal with window management. That is a function of the 2D X server. VirtualGL takes the 3D commands that normally would have been sent to the 2D X server, and it redirects them to a Pbuffer on the 3D X server, then reads them back at the appropriate time and displays them to the 2D X server (either directly or via intermediate compression/transmission using the VGL Transport.) ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
