ABSTRACT

RFB (Remote Frame Buffer) protocol enables remote users to share the desktop of the server either exclusively or on a sharing basis.

RFB (remote frame buffer) is a simple protocol for remote access to graphical user
interfaces. Because it works at the frame buffer level it is applicable to all windowing
systems and applications, including X11, Windows 3.1/95/NT and Macintosh.
The remote endpoint where the user sits (i.e. the display plus keyboard and/or pointer) is
called the VNC client. The endpoint where changes to the frame buffer originate (i.e. the
windowing system and applications) is known as the VNC server.

RFB truly a thin client protocol. The emphasis in the design of the RFB protocol is
to make very few requirements of the client. In this way, clients can run on the widest
range of hardware, and the task of implementing a client is made as simple as possible.



Existing System
In the present scenario of distributing information using a Client “ Server environment there exist communication mechanisms such as TELNET etc. These are only character based in nature and do not provide an easy way for communication across network. Also the communication may not always be platform independent. We need a protocol that can well support GUI-based client-server interaction and allows multiple clients to share the desktop of the server.

Proposed System
The RFB (Remote Frame Buffer) protocol was proposed by Tristan Richardson and Kenneth R. Wood, ORL, Cambridge in January 1998. The protocol is based around a single graphics primitive: put a rectangle of pixel data at a given x, y position.
The RFB relies on sending encoded pixels to the client that contains the information of the Server Desktop. The client then decodes the pixels and draws them on a graphical application running on its machine. Events occurring at the client side are trapped and sent to the Server where the changes are reflected.
For this purpose the RFB protocol suggests the use of a Frame Buffer. The Frame Buffer actually contains the desktop information which is updated when the client generates an event. This updated buffer must be sent to the Server which updates its own desktop accordingly. Similarly when the Server generates events that affect the desktop, the updated buffer is redrawn at the Client. This provides a synchronized desktop sharing facility.



Procedure

VNC consists of two types of components. A server, which generates a display, and a viewer (client ), which actually draws the display on your screen. There are two important features of VNC:
The server and the viewer may be on the different machines and on the different architectures. We expect the most common use to be the display of UNIX X desktop on a PC, for example. The protocol, which connects the server and the viewer, is simple, open, and platform independent.
No state is preserved at the client end. Breaking the viewerâ„¢s connection to the server and then reconnecting will not result in any loss of data. Because the connection can be remade from somewhere else, you have easy mobility.
So, to get started with VNC you need to run a server, and then connect to it with a viewer . the VNC software requires a TCP/IP connection between the server and the viewer, though there is no reason why the software couldnâ„¢t be modified to use ,for example ,RS232 or Firewire. But for now weâ„¢ll need to know the name or the IP address of the server machine.

In VNC RFB protocol allow server to update the frame buffer displayed on a version. When the connection between a client and server is first established the server begins by requesting authentication from the client using a challeng_response scheme which typically results in the user being prompted for password at the client end .the client then requests and update for the entire screen and the session begins. Because of the stateless nature of the client either side can also the connection at any time without adverse consequences. The protocol is designed to make the client as simple as possible, so it is usually up to the server to perform any necessary translations.

Most people will be running either a Unix server or a Windows server, though similar principles will apply to other platforms.

1.4 Requirements Specification:
The technical aspects of the Software Hardware are as follows:
Hardware Required:
Independent of platform: Since the project is done using JAVA feature, it has acquired a great feature of JAVA: Platform Independent. So any special hardware not required. It works in any platform that supports JDK1.2.2 or advanced version.
Minimum of 32MB RAM is required. But 64MB is recommended for better performance.
15MB Hard disk space is required to install the project.
All network hardware is required.
Software Required:
JDK1.1.7 or any advanced version.
JSDK 2.0
Language Used :
JAVA
§ Java Applets
§ Java Sockets
§ AWT

RFB PROTOCOL
B.Tech Seminar report
by
Saurabh Santhosh
Department of Computer Science And Engineering
Government Engineering College, Thrissur
December 2010

[attachment=8384]

Abstract
Remote Desktop Softwares are those softwares which provide Remote Access. Remote
Access means the ability of a user to log onto a remote computer or network from a
distant location. This usually comprises of computers, a Network, and some remote
access software to connect to the network. Since this involves clients and servers connected
across a network,a protocol is essential for efficient communication between
them. RFB protocol is one of such protocols which is used by the client and servers
for communicating with each other and thereby making Remote Access possible.
The purpose of this Paper is to give a general idea as to how this Protocol actually
works. This paper also gives a broad idea about the various messages of this protocol
and how these messages are send and interpreted by the client and server modules.
This Paper also includes a Simple implementation of the Protocol which shows the
various messages and methods and how this protocol is practically used for gaining
remote access.

Chapter 1
Introduction
RFB (remote framebuffer) is a simple and efficient protocol which provide remote
access to graphical user interfaces.As its Name Suggests it works at the framebuffer
level and thus it is applicable to all windowing systems and applications. Eg. X11,
Windows and Macintosh. It should also be noted that there are other Protocols available
and RFB is the protocol which is used in Virtual Network Computing (VNC)
and its various forms. Due to increase in number of Software products and Services
such protocols play a very important role nowadays.

Chapter 2
REPRESENTATION OF PIXEL
DATA
The Interaction between server and client begins with a negotiation of the format and
encoding which will be used to send the pixel data. This step is included to make the
job of client easy. The server must always be able to supply the pixel data in the form
the client needs. In case the client can handle different formats,client can choose any
one it wishes. That is why this protocol is called a thin-Client Protocol.
Pixel Format refers to the representation of various individual colors by pixel values.
The most common formats are 24-bit or 16-bit where bit-fields translate directly
to the primary colors , and 8-bit color map where a mapping can be used to obtain
RGB intensities.
Encoding refers to how a rectangle of the above said pixel data will be sent across
the channel. Every triangle of this pixel data is prefixed by a header which contains
the X,Y position of the rectangle on the screen,the width and height of this triangle,
and an encoding type which specifies how the pixel data is encoded. In practice
we normally use only the ZRLE, Hextile and CopyRect encodings since they provide
the best compression as far as typical desktops are concerned.

where is the source code

hi
if there is source code , it should be in the attached file. please check it out.

i need full seminar report and ppt for remote frame buffer protocol..pls

i need slide presentation of RFB.:::

plz send me full presentation slides of "RFB protocol".

To get more information about the topic "RFB (Remote Frame Buffer)" please refer the page link below
http://studentbank.in/report-rfb-remote-frame-buffer