Editing Rich client

{{Short description|Type of client over a network powerful enough to perform significant computation}}{{EngvarB|date=January 2019}}{{Refimprove|date=April 2007}}
In [[computer network]]ing, a '''rich client''' (also called a '''heavy''', '''fat''' or '''thick client''') is a [[computer]] (a "[[Client (computing)|client]]" in [[client–server]] network architecture) that typically provides rich functionality independent of the central [[Server (computing)|server]]. This kind of computer was originally known as just a "client" or "thick client,"<ref>{{cite web|url=http://www.techterms.com/definition/thickclient|title=Thick Client Definition|website=www.techterms.com}}</ref> in contrast with "[[thin client]]", which describes a computer heavily dependent on a server's applications. A rich client may be described as having a '''rich user interaction'''.<ref>{{Cite web |url=http://www.phpbuilder.com/columns/ajax_excerpt.php3 |title=Rich User Interaction of Ajax |access-date=2018-12-23 |archive-url=https://web.archive.org/web/20170919141615/http://www.phpbuilder.com/columns/ajax_excerpt.php3 |archive-date=2017-09-19 |url-status=dead }}</ref>

While a rich client still requires at least a periodic connection to a network or central server {{citation needed|date=August 2020}}, it is often characterised by the ability to perform many functions without a connection.  In contrast, a thin client generally does as little processing as possible on the client, relying on access to the server each time input data needs to be processed or validated.

== Introduction ==
The designer of a client–server application decides which parts of the task should be executed on the client, and which on the server.  This decision can crucially affect the cost of clients and servers, the robustness and security of the application as a whole, and the flexibility of the design for later modification or [[porting]].

The characteristics of the user interface often force the decision on a designer.  For instance, a drawing package could require the download of an initial image from a server, and allow all edits to be made locally, returning the revised drawing to the server upon completion.  This would require a rich client and might be characterised by a long delay to start and stop (while a whole complex drawing was transferred), but quick to edit.

Conversely, a thin client could download just the visible parts of the drawing at the beginning and send each change back to the server to update the drawing.  This might be characterised by a short start-up time, but a tediously slow editing process.

=== History ===
The original server clients were simple text display terminals including [[Wyse]] [[Computer terminal|VDU]]s, and rich clients were generally not used until the increase in PC usage. The original driving force for thin client computing was often cost; at a time when CRT terminals and PCs were relatively expensive, the thin-client–server architecture enabled the ability to deploy the desktop computing experience to many users. As PC prices decreased, combined with a drop in software licensing costs, rich client–server architectures became more attractive. For users, the rich client device provided a more-responsive platform and often an improved [[graphical user interface|graphical user interface (GUI)]] than what could be achieved in a thin client environment.{{Citation needed|date=May 2020}} In more recent years, the Internet has tended to drive the thin client model despite the prodigious processing power that a modern PC has available.{{Citation needed|date=June 2008}}

=== Centrally hosted rich client applications ===
Probably the thinnest clients, sometimes called "ultra thin," are [[remote desktop]] applications, e.g. the [[Citrix]] products, and [[Microsoft]]'s [[Remote Desktop Services]], which effectively allow applications to run on a centrally-hosted virtual PC and copy keystrokes and screen images between the local PC and the virtual PC. These ultra-thin clients are often used to make available complex or data-hungry applications that have been implemented as rich clients but the true client is hosted very near to the network server.{{Citation needed|date=June 2008}}

== Advantages ==
*'''Lower server requirements'''. A rich client server does not require as high a level of performance as a thin client server (since the rich clients themselves do much of the application processing). This results in drastically cheaper servers.
*'''Working offline'''. Rich clients have advantages in that a constant connection to the central server is often not required.
*'''Better multimedia performance'''. Rich clients have advantages in multimedia-heavy applications that would be bandwidth intensive if fully served. For example, rich clients are well suited for [[video gaming]].
*'''More flexibility'''. On some operating systems software products are designed for personal computers that have their own local resources. Running this software in a thin client environment can be difficult.
*'''Using existing infrastructure'''. As many people now have very fast local PCs, they already have the infrastructure to run rich clients at no extra cost.
*'''Higher server capacity'''. The more work that is carried out by the client, the less the server needs to do, increasing the number of users each server can support.
*'''Require more resources but fewer servers'''.

== See also ==
* [[Diskless node]]
* [[Rich client platform]]
* [[Thin client]]
* [[Edge computing]]

==References==
{{Reflist}}

{{Computer sizes}}

[[Category:Clients (computing)]]
[[Category:Computer output devices]]
[[Category:Microcomputers]]
[[Category:Networking hardware]]