
G&R
Overview
G&R product architecture
The G&R products are built in a modular way, and designed to take advantage
of the multitasking capability of the Windows and UNIX/Linux platforms.
Thus a single instance of a product will in general consist of two or three quite
separate processes:
• A video handler: which maps all updates of the internal screen image
into the control sequences required to update the specific screen being
used. The video handlers are used by UNIX/Linux products, which must
communicate with various different terminal types. The Windows
products use the standard Windows graphical interface.
• A product: for example an emulator, which updates the internal screen
image to duplicate the terminal being emulated. The product will also in
general send and receive data to the host system using the global inter-
face, which applies to all communications protocols.
• A line handler: which maps the global communications interface into the
specific line protocol being used.
This structure has proven itself extremely efficient and very robust. We are able
to develop a video handler for a new screen type, and we know that once it
works with one G&R product it will work with all. We are able to develop a
new line handler and know that once it works with one product it will work
with all. We are able to develop a new product using a given screen and
communications protocol, and know that the product will work with all screen
types we support, and with all the communications protocols we support.
The server programs (e.g. Ggate, Gspool, GUFT) differ slightly from the
above model, as they don’t need a video handler, only a line handler. Pthru
doesn’t need a video handler either; it needs one line handler to connect to the
host and one line handler (TTY) to pass all presentation data through to the
terminal.
Gline Line Handlers and Configuration
5
Kommentare zu diesen Handbüchern