On 3/22/06, Ruben Safir <[EMAIL PROTECTED]> wrote: ... > > > > Help me understand this X stuff. Is this conceptually different from > > VNC/VNC server? > > Yes - its entirely different and VNC on Unix just another X instance > without all the capabilities of X. > > In its simplest basic design, you have an X server. An X server runs on > yourhostA and listens for a client to run. It then displays the > programs your asking it to run on a determined display and screen. A > client is any program have has the ability to display in X. The X > server understands calls and events. In response to these requests is > makes graphic displays and responds device events (such as a mouse and a > cursor) connected to a terminal. The X server understands network > requests and talks TCP/IP and Unix Sockets and knows cryptography. >
Reuben, Thanks for the detailed response. You have provided valuable information about how to configure and setup X. But in the end it still seems that it is just a method for displaying output for programs, and managing input from the user (keyboard, mouse). So to me it seems that VNC is conceptually the same--a way to interact with a remote computer. Yes X seems more sophisticated and likely is more functional. The issue then would seem to be one of bandwidth utilization. I'm not sure which would use less--VNC which essentially sends an *image* of the screen, or X which would send drawing instructions to the X server. Kevin ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
