2012/11/7 DRC <dcomman...@users.sourceforge.net>: > You would write a transport plugin. The API is described in > /opt/VirtualGL/include/rrtransport.h (NOTE to self: I really need to > Doxygen that at some point.) Since transport plugins are responsible > for allocating memory to receive each frame from VirtualGL, your plugin > could allocate a shared memory segment or segments, thus allowing > another process to access the same memory (assuming it knew the segment ID.) > > Again, though, this just gives you access to the rendered 3D pixels. > The rest of the GUI from the application gets rendered by the 2D X > server, and VirtualGL has nothing to do with it. >
I've been thinking about this a bit. if i could access the final image that the turboVNC client displays that would work too assuming that: 1) turboVNC renders wm widgets locally in the client 2) turboVNC composites the opengl renderings from the server in the windows if i could get turboVNC to offer the final display as, say, a shared memory segment in the client machine, that would work perfectly is that possible? ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
