fat client

Of all the various options, File Transfer and a fat-client application produced and supported by GC called ESA-Link are the most popular.

A fat client is robust from a coding point of view, but a thin policy can then be applied to the data application.

Fat-client systems simply do not scale to the thousands or millions of users that Web-based systems may have.

A fat client application's enhanced performance comes at the expense of a significant initial download and installation.

And two-tier systems perform poorly when a fat client must connect to a database over the WAN.

Recently we were given the assignment to reduce the memory footprint of a fat client.

An extreme fat client downloads the entire application and only calls the server when data needs to be exchanged.

The application developed in this tutorial is targeted at internal users accustomed to using a traditional fat-client terminal emulator.

If you want to get the maximun benefit out of your user interface, then you want a solution based on a fat client.

Traditional "fat client" solutions require the application to manage access to shared data at the database level.

Also, each client machine has a Geronimo fat-client application executing inside the client application container.

This application is a Java swing application that can be run on a FAT client machine on the network.

Is Microsoft irretrievably addicted to its old-fashioned, fat client and fat license view of the world?

While the rich client lies between the thin client and the fat client, it comes in many gradations.

With a client-server application, you have a wide spectrum of implementations, from fat client to thin client.

A fat client is essentially an application that runs on the client.

While the term "fat client" often is used to mean an ordinary GUI client application, in this case the client was nearing obesity.