About Thin Client Computing

About Thin Client Computing

Thinclient.org has been in existence since around 2004.  The site is managed by Craig Keefner who has extensive experience with configuring, monitoring and maintaining thin clients in the unattended self-service industry.

In November 2014 we migrated our Content Management System from the original Movable Type (which served us well) to WordPress (which actually copied a ton from Movable Type).

Originally while at Northgate in the early 90s Craig first began working with thinclient systems being developed by Citrix as well as the old SCO Xenix terminals. Not a big fan of Novell.

About the Editor

craig keefner

Working for Olea Kiosks and Kiosk Information Systems and focused on transactional systems for self-service (QSR, Fast Casual, Healthcare, Telemedicine, bill payment and more). Experience as web programmer (NW Airlines), Bridal Kiosks (Target Clubb Wedd and Gift Certificate Company). Irwin Jacobs B2C. Eleven years with Kiosk Information Systems. Major projects include: Verizon, Army Gaming Centers, Target Store Bridal Registry, Correctional visitation, AT&T and many more.

The pre-Wordpress archives are located at https://thinclient.org/thinclient-news/  

We’ll include the hyperlink for now and see how Google, Semrush and AHREFs digest all the old Movable Type content.


About Thin Client Computing

Since 1999, Thinclient.org has been reporting the thin client computing market as well as the ChromeBook, Zero Client, Android clients, Pi Raspberry Clients and Thick Client market. Generally the cloud computing market since it started with companies such as Citrix back in the late 80s.

A thin client is a lightweight[vague] computer that has been optimized for establishing a remote connection with a server-based computing environment. The server does most of the work, which can include launching software programs, performing calculations, and storing data. This contrasts with a fat client or a conventional personal computer; the former is also intended for working in a client–server model but has significant local processing power, while the latter aims to perform its function mostly locally.

Thin client hardware generally supports a keyboard, mouse, monitor, jacks for sound peripherals, and open ports for USB devices (e.g., printer, flash drive, webcam). Some thin clients include legacy serial or parallel ports to support older devices such as receipt printers, scales or time clocks. Thin client software typically consists of a graphical user interface (GUI), cloud access agents (e.g., RDP, ICA, PCoIP), a local web browser, terminal emulators (in some cases), and a basic set of local utilities.

New hardware interfaces include socket-based enabled devices eliminating the need for a physical USB connection. Bluetooth wireless connectivity is also a big factor for devices.