On 11/7/12 6:54 AM, charles quarra wrote: > Ok I see. Let's assume for a moment that i'm interested in running many > openGL > applications at once, and i want to provide access to each application > context buffer > (i'm not sure how you would call the buffer that represents what the > user actually sees > and what i understand that VirtualGL sends over the wire): > > What would i have to do in order to achieve that? Is there an api to > access that from a separate process > running in the rendering service? or do i need to modify some existing > VirtualGL service?
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. ------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
