The central feature of client/server architecture is the allocation of application tasks between clients and server. In both client and server the basic software is an operating system running on the hardware platform. The platforms and the operating systems of client and server may differ.

There may be a number of different types of client platform and operating systems and a number of different types of server platforms and operating systems in a single environment. As long as a particular client and server share the same communications protocols and support the same applications, these lower-level differences are irrelevant.

It is the communications software that enables client and server to interoperate. TCP/IP, OSI are some examples of communications software. The point of all of this support software (communication and operating systems) is to provide a base for distributed applications. Ideally, the actual functions performed by the application can be split up between client and server in a way that optimizes platform and network resources and that optimizes the ability of users to perform various tasks and to cooperate with one another in using shared resources. These requirements dictate that the bulk of the applications software executes at the server, whereas most of the application logic is located at the client in other cases.

An essential factor in the success of a client/server environment is Continue reading »

There is a spectrum of implementation that divides the work between client and server differently. Processing can be allocated in a number of ways. There are several major operations for database applications. They are host based processing, server based processing, client based processing, and Cooperative based processing.

Host based processing is not true client/server computing. Rather, host based processing refers to the traditional main frame environment in which all or virtually all of the processing is done on a central host. Often the user interface is through a dub terminal. Even if the user is employing a micro computer, the user`s station is generally limited to the role of a terminal emulator.

The most basic class of client/server configuration is one in which the server is principally responsible for providing a graphical user interface, whereas virtually all of the processing is done on the server. This configuration is typical of early client/server efforts, especially departmental-level systems. The rationale behind such configurations is that the user workstation is best suited to provide a user-friendly interface and those databases and applications can easily be maintained on central systems. Although the user gains the advantage of a better interface, this type of configuration does not generally lend itself to any significant gains in productivity or to any fundamental changes in the actual business fun Continue reading »