dbind VNC Client

VNC Client can show the desktops on remote computers and can control them by local mouse and keyboard.

The client needs a VNC server to be run on the remote computer. RFB (Remote Frame Buffer) protocol is used for communication between the client and the server over the network. The mouse movements and keyboard events are transmitted from the client to the server where they are reproduced. The server screen output is relayed back and displayed on the client. Thus users can control remote computers using a local one as terminal.

VNC is abbreviation of Virtual Network Computing. This is the popular name of the RFB based desktop sharing systems.

dbind VNC Client is written in Java™. That means that it runs on almost every operating system including but not limited to: Windows (98, ME, NT, 2000, XP, 2003, Vista), MAC OS X (10.2.3+, 10.3.x, 10.4.x, 10.5.x, etc), Solaris, Linux (with X Window System - KDE, Gnome, Xfce, etc.).
It is fast and very small - it is about 27k. No joke.

dbind VNC Client is under development and currently implements not all of the encodings defined in RFB v3.8 protocol specification. Regardless of that it functions pretty well because during the initial handshaking with server, they agree to use only the encodings which are supported form both the client and the server.

Remote Frame Buffer v3.8 protocol implementation

	Initial Handshaking Messages
	• Protocol Version		Y
	• Security
	- None		Y
	- VNC Authentication		v3.3
	• Security Result
	• Client Initialisation		Y
	• Server Initialisation		Y

	Client to server messages
	• Set Pixel Format		N
	• Set Encodings		Y
	• Framebuffer Update Request		Y
	• Key Event		Y
	• Pointer Event		Y
	• Client Cut Text		N

	Server to client messages
	• Framebuffer Update
	- Raw encoding		Y
	- CopyRect encoding		Y
	- RRE encoding		Y
	- CoRRE encoding		N
	- Hextile encoding		N
	- ZRLE encoding		N
	• Set Color Map Entries		N
	• Bell		Y
	• Server Cut Text		N

	Pseudo-encodings
	• Cursor pseudo-encoding		Y
	• Desktop Size pseudo-encoding		N