<div class="gmail_quote">On Wed, May 25, 2011 at 3:07 PM, Alan Coopersmith <<a href="mailto:alan.coopersmith@oracle.com">alan.coopersmith@oracle.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">On 05/25/11 12:53 PM, David Jackson wrote: > X.org needs to listen to users on X Window System flexibility. </div>X.Org does listen, but we don't have developers sitting around with nothing to do, but instead have far more things to work on than people volunteering to work on them. <div class="im"> > A display driver that contains a VNC server. The problem with x11vnc is that it > is slow, very slow. XVnc server, which is a X server that contains a VNC server > but has no hardware drivers, is much faster since the VNC server is built > directly into the X server, however this does not allow one to export their main > X display which is also displayed directly to video hardware. The solution here > is to include a driver in the X.org main server distribution for a VNC server > that can be loaded into the X server. The VNC server driver should be able to be > dynamically loaded while the server is running and the output of the server > displayed simultaneously to VNC clients and to the local video hardware. </div>TigerVNC provides a vnc.so loadable module for the X.org server already that does this. <div class="im"> > Dynamic runtime enabling and disabling, configuration and setup and removal of > display output and input drivers while the server runs without server restart. </div>Done for input drivers several years ago. Output drivers is a much harder problem. <div class="im"> > While improving and enhancing programming facilities availaible to developers > and enhancing features and flexibility to users, X.org needs to commit to full > backwards compatability with the X11 protocol and the extensions to it, > including binary compatable at the protocol level and backwards compatability at > the xlib API level. </div>The core protocol & Xlib API has been completely backwards compatible for 24 years now - how much better can we get? (Sorry, the rest was way too long, and given that it's clear you're not even aware what's already being done, I doubt anyone is going to trudge through it all.) -- -Alan Coopersmith- <a href="mailto:alan.coopersmith@oracle.com">alan.coopersmith@oracle.com</a> Oracle Solaris Platform Engineering: X Window System </blockquote></div> Alan, I looked for information on vnc.so on Tightvnc's website. There are no instructions or documentations there on how one would even use it. I suspect it probably wouldnt work at all if it exists, or would be difficult or impossible for a user to get it to work. X.org should ship a driver for VNC server access. This is something that everyone could use. Again, it is important that X be flexible and useable, otherwise its not really useable. Many people need network transparency and may want to have many X servers running, maybe a headless one with only VNC server in it, maybe one with both VNC server and display to hardware. Xvnc is quickly becoming useless. KDE apps no longer really work with it anymore. x11vnc is useless and too slow. Why not add flexibility and options so X is not so limited in how it can be used?