x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way x11vnc plays the role for Unix/X11 that WinVNC plays for Windows.

I wrote x11vnc because x0rfbserver was basically impossible to build on Solaris and had poor performance. The primary x0rfbserver build problems centered around esoteric C++ toolkits. x11vnc is written in plain C and uses only standard libraries. I also added a few enhancements to improve the interactive response, add esoteric features, etc.

For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a physical display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop.

The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol (the exception is cached pixmap data on the viewing-end). Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.

What's New in This Release:

· This release provides client-side caching to improve interactive response. Almost no VNC viewers implement caching which is why VNC is slow compared to other remote graphics protocols.
· The x11vnc caching will work with any VNC viewer, but they will not hide the pixmap cache region that is below the main desktop (one must adjust the window manually). The SSVNC Unix VNC viewer, however, automatically detects and hides the region.
· To enable caching, supply "-ncache n" to x11vnc, where the number n, e.g. 10, indicates how much memory to devote to the caching scheme.