Also: FatClient, ThickClient, RichClient.
(FatClient & ThickClient may be considered pejorative by some: RichClient is more positive)
A term whose meaning has become muddied over time, a FatClient system may be one where
Plug-ins that can automatically install on the client system is the grey area. Other than that, the usual distinction between fat/thin is whether you need to install a client or not (with the assumption that the client already has a browser), so a heavy JavaScript app is considered "thin". The browser assumption is natural since the term ThinClient comes from the marketing of web-based applications.
The alleged advantage to fat clients is less load on the server and faster response to user input. Alleged downsides include more desktop "babysitting" to keep the client software up-to-date and configured properly, and more SecurityManagement concerns because the business rules are on the client instead of on the server hidden behind protocols.
AJAX, in my view, enables FatClient web applications. Is a desktop application that relies on one or more servers no longer a "desktop application" because of said reliance? Here's my list of things that differentiate FatClient:
And therefore RichInternetApplications are FatClients??