From: Jeremy W. <jw...@co...> - 2012-06-07 03:39:04
|
> My project (TurboVNC) is an Xvnc implementation that builds upon the > TightVNC and xf4vnc code bases, with numerous codec enhancements (the > same ones that went into libvncserver 0.9.9) to allow it to achieve very > high levels of performance. Yes, it contains XFree86 code, but that > code has undergone numerous modifications and bug fixes over the years, > so it is quite stable and is being actively deployed to tens of > thousands of users worldwide (including entire companies who use > TurboVNC, in combination with VirtualGL, to eliminate the need for 3D > workstations entirely, saving themselves millions of dollars a year.) > It's under active development and testing all the time, and since we > have complete control over our X server code base, it's relatively easy > to fix issues if they arise. Ah, very interesting; I was unaware of virtualgl. I'm currently primarily interested in 2D issues, but that could be quite handy. Another clue bat, if you don't mind - am I right that if you were to reinvent it today, you'd implement it as an xorg driver module, rather than including all of X? (Presuming that upstream xorg would be receptive to any tweaks needed). Or are there benefits inherent in controlling all of X that you wouldn't want to live without? Cheers, Jeremy |