A fat client (also called rich client and thick client)
|“||does as much processing as possible and passes only data for communications and storage to the server.||”|
A fat client still requires at least periodic connection to a network or central server, but is often characterized by the ability to perform many functions without that connection. In contrast, a thin client generally does as little processing as possible and relies on accessing the server each time input data needs to be processed or validated.
- AR 25-1, at 130.
|This page uses Creative Commons Licensed content from Wikipedia (view authors).|