 |
|
 |
 |
 |
| What is thin client
computing? |
|
The term
thin client originated in the 90's to describe a new
category of client devices such as Network Computers,
X Terminal (supporting X Window Systems) and Windows-based
Terminals (WBTs) that run "thin" operating
systems locally.
Today,
the term thin client computing defines a
network-based approach to information processing where
all applications and data are centrally hosted on a
server and accessed using a simple terminal, referred
to as a thin client. Thin client are comprised
of both cost-effective hardware devices and software
elements that provide customers with access to centrally-controlled
applications. This
is different from a client-server architecture where
some of the data and applications reside on PC’s spread
throughout the organisation. Because no applications
or data are resident on the desktop, it is "thin"
when compared to the traditional "fat" PC.
|
| How
does thin client computing differ from the terminal-mainframe
approach of the 60's? |
|
Apart from the very simple
desktop management and elimination of frequent desktop
upgrades, thin client computing differs greatly from
the mainframe-terminal model in three primary ways:
Access
to all network operating environments: thin client
computing provides simultaneous network-based access
to applications running in multiple environments—including
Windows, UNIX, Linux, legacy, and Java—from one thin
terminal. The mainframe computing model usually provided
a connection between the terminal and one mainframe
host only.
Local
processing: while character terminals provided
very rudimentary local capabilities, the thin clients
contain powerful CPUs that are used for a variety of
display and input-output functions and also run local
emulators, a web browser and Java-based applications.
Keynux thin clients are also designed to run applications
locally.
Graphical
desktop iInterface: ASCII character terminals
provided access primarily to character-based applications
while the thin clients present a user with the familiar
Windows or X Window graphical user interfaces (GUIs)
and provide full multimedia support for video, audio
and high-resolution imaging.
|
| The different forms
of server based computing |
|
Thin
clients can access many different types of server based
applications on practically any operating environment,
whether Unix, Linux, Windows® or legacy systems.
Such applications
can be divided in three categories:
- X Window System
applications,
- Web based or Java
applications,
- Legacy applications on
mainframe computers also known as green screen applications.
X Window
System applications
With
this architecture, data and applications are hosted
on the servers. If for most manufacturers, thin client
computing is limited to applications centrally processed
on servers and remotely accessed using a simple graphics
based terminal, Keynux approach is different.
With
Keynux thin client architecture, the following two modes
of operation are supported:
- Remote
processing: data and applications are
resident on the server; at execution, applications
are then run on the server and both data and applications
are remotely accessed from the thin client, through
the network. With this mode, the thin client behaves
as a simple graphics based terminal in charge of
local display processing. Such a mode requires a
strong server and a large network bandwidth.
- Local
processing:
data and applications are resident on the server,
but at execution, the applications are uploaded
in the thin client memory to be executed locally.
All data are centrally saved and stored on the server.
Such a mode optimizes the network bandwidth and
the applications server load, but requires sufficient
memory size at thin client level.
Keynux
thin clients can support both execution modes concurrently.
This means that some applications can be executed remotely
while others are executed locally. It is the role of
the systems administrator to define which applications
must be executed locally or remotely, to optimize servers
load, network bandwidth and end-user's productivity.
Web
based computing
Web based
computing is where applications are deployed using a
form of HTML (ie HTML, XML or Dynamic HTML), Java or
a mixture of both. Applications and data are hosted
on central servers and are connected to the web. Web
browsers can then be used to access the application.
The architecture doesn't use the same protocol as X
Window System computing, but a protocole such as HTML
to transmit screens. Some applications can also be run
locally if Java is used. All Keynux thin clients contain
built in web browsers for easy access to web based applications.
With web based applications, security must be reenforced
to protect companies against hacking and unwanted intrusion
into corporate networks.
Legacy
applications (green screen applications)
This
form of server based computing refers to older mainframe
or mini-computer applications running centrally and
accessed using ASCII text terminals. This form of server
based computing is in decline, being replaced by Unix-,
Linux- or Windows-based Client/Server or web based architectures.
|
| Why chosing Keynux
thin clients? |
|
The Keynux
thin client infrastructure is a complete, end-to-end
solution - not just devices, not just client management
software - for accessing, delivering, and managing information
over networks. It ensures ease of deployment and use,
high-end service and support and provides critical functionality
on the desktop.
Thin
client computing translates to simpler, more cost effective
access to information. It is great for organisations
with PC’s who want to have access to their traditional
applications while getting rid of the cost and hassle.
Ease of management, rapid deployment and outstanding
reliability are the key
benefits of thin client computing. These benefits
are currently driving the market growth.
|
|
| |
|
|
|
|
| |
| |
|
 |