Many of today’s computer networks are based on the client/server concept. An example of a client is a desktop computer running Windows 95/98/NT. By itself, the client is capable of running programs, displaying information to the user, etc. A server is a more powerful central computer that stores things of interest to those people on the network. It might store important files, a database, or applications used by many people. In the case of business data and transactions, particularly in light of OLTP and transaction "rollback", it makes more sense to store these things centrally than to have them scattered around the network. It also makes administration of the network easier.

Generally, the client/server concept works like this. When a client needs to use something that resides on the server, it sends a request across the network. The server then processes the request and sends the requested data back to the client, where it may be processed further to meet the user’s needs. Distributing the burden of processing between the client and server, while maintaining central file storage, allows for optimal use of network resources. In the future the notion of a "thin client" and distributed processing may replace the need for software programs on the client.

FAMOUS is built upon this client/server concept. The FAMOUS database resides on a central server, while the FAMOUS application resides on the client. This allows the client machine to handle the burden of running the application, while the server’s resources are used to perform complex data processing. The client may then perform final processing of data retrieved from the server. This "division of labor" allows FAMOUS programmers to put application logic, or "code" wherever it makes the most sense, and utilizes your network resources to their fullest. FAMOUS is well positioned to take advantage of future changes in distributed processing technology.

System Requirements