This is different from the traditional fat client, which is a computer designed to take on these roles by itself.

The data is then retrieved via web browsers or fat clients.

The doctors might retort, "When did you see a thin lawyer, or a fat client?"

This is accomplished via thin and fat client technology.

This also means that the nodes themselves are less likely to have hardware failures than fat clients.

A typical desktop PC is usually considered a fat client.

End user productivity still suffers compared to a well maintained fat client desktop.

Administration is also typically done through browser-based interfaces, but some systems require the use of a fat client.

This is desirable in contexts where individual fat clients have much more functionality or power than the infrastructure requires.

Similar to a fat client, it processes locally, but relies on the server for storing persistent data.

The fat client is most common in the form of a personal computer, as the personal computers or laptops can operate independently.

It can be used to write not just traditional "fat client" applications, but also middleware and web applications.

The GUI is a fat client connecting to the database.

The term thin client was also not well established among IT professionals, most of whom had been working on fat client systems.

Originally, a small number of security and system setup functions still needed to be performed on a fat client machine; however, this is no longer the case.

A fat client refers to a device that has sufficient speed and size to run programs and is loaded locally with software needed for operation.

Greater network bandwidth (i.e. capacity) will also be used in a diskless model, compared to a fat client model.

In one classification, client computers and devices are either fat clients, thin clients, or hybrid clients.

This approach offers features from both the fat client (multimedia support, high performance) and the thin client (high manageability, flexibility).

The local CPU and RAM is used on the fat clients, which provides a few benefits.

In addition to the fat client email clients and small email clients, there are also Web-based email applications called webmail.

In process access to Ingres NET for FAT clients making distubution easier.

A fat client still requires at least periodic connection to a network or central server, but is often characterised by the ability to perform many functions without that connection.

Hubbard and White also inherited the matter of what to do with his name-appending it to theirs had been the price for both the colonel and his fat clients.

In any case this is also a problem which can affect any client-server network to some extent, since, of course, fat clients also use servers to store user data.