What Is A “Thin Client”?
The term thin client sometimes means hardware and sometimes software elements. In the material sense, a thin client is a computer in client-server architecture, and which has almost no application logic. This computer depends mostly central server for processing.
A thin client can be satisfied with a minimalist machine in terms of material:
- A computer (very) old.
- A modern computer.
- A computer created to make the thin client (WYSE manufacturers like Sun, HP and NEC do).
Thin client software within the meaning:
Example of thin client software in the sense: a Web browser is a universal client, particularly when an applet is downloaded. For the with a Web browser, the practice is a thin client application, even if it must be equipped with plugins or virtual machine (for Java applets). As part of “web” application, the thin client is the Web browser. But we can also talk about thin clients to designate terminals RDP (Remote Desktop Protocol) or Citrix Metaframe, application use of Microsoft Windows, or 2X or DotRiver X terminals for UNIX systems.
For example, the draft LTSP (Linux Terminal Server Project) will establish a network of Linux servers and thin clients, which are converted into computer terminals.
Interest in thin client:
The prevailing logic in the deployment of thin clients is essentially economic logic. This reduces the total cost of ownership and management. However, do not forget a certain ecological dimension in the case of recycling of old computers into thin-clients hardware.
- In web applications, the use of thin client simplifies work by eliminating the need to distribute and install client software on users’ machines. These programs continue to exist on the workstation. These applications require operating in a secure location (Java sandbox) within the browser. These software programs called applets to run on an OS features more or less restricted / secure virtual machine called Flash, Silverlight, and Java. These virtual machines can have a thin client and rich.
- As part of customer equipment, thin clients are much less prone to breakdown compared to PCs, they run on a processor that heats and just generally do not drive. Furthermore, when there is need for change, just change the central server. On the other hand, the administration is much more centralized, and therefore requires less staff (but qualified). In cons – party uses a lot of bandwidth and allows the use of software in connected mode where the concept of Google Gears.
Examples Of Thin Client Application
- Among the most popular thin clients are Wyse Terminals, HP, NEC and Suns. Some are equipped with Windows Mobile CE, or a light version of Linux. The initialization of the terminal is very rapid and virtually instantaneous. However, the use of thin clients such is not suitable for heavy duty applications (development, 3D) installed on the server. Unless you have oversized one in memory size and processor speed (for 50 concurrent users allow a minimum of 16 GB of RAM). By cons for internet and office use this solution is ideal (for 50 concurrent users require 8 GB of RAM).
- Outside of thin clients listed above, it is quite possible to recycle old computers (without hard drive) to thin clients connecting to a Linux server using LTSP on a server or DotRiver. For this, the workstation must be able to connect to the server via its NIC. There are several possibilities: either the network card is able to “boot” on the network is to tell the server to retrieve the necessary files, or it can not do in which case it will start it (see draft Etherboot) through a special diskette, CD-ROM, hard disk or even a USB device (for older computers with older BIOS permitting). This may be quite possible for example schools that do not need very powerful machines that can cost effectively convert obsolete equipment.
Study: From Wikipedia, the free encyclopedia. The text is available under the Creative Commons.
- Cloud Computing: The Concept and Examples of its Virtual Services | Part 1 - July 23, 2012
- Why Rapidly Growing Companies Need Cloud Computing | Part 1 - July 22, 2012
- Web Designing Process | Strategic Planning | Part 1 - August 7, 2011