Java Reference
In-Depth Information
to manage the user interface (UI) as well as the data validation part of the application. Also,
many client processes are designed to execute business logic, partly or fully, on the client side,
before forwarding the request to the server process. he client process gathers the data from the
user through local resources such as the monitor, keyboard, mouse, track-pad, and so on, on
the client system. A client process may use a text-based user interface or a graphic-based user
interface (GUI).
An enterprise supports a number of clients, and a client can connect to multiple servers for
meeting speciic business requirements in a LAN, WAN, or MAN environment.
1.1.2.3 Client/Server Architecture
In its simplest manifestation, the client/server architecture represents a server system networked
with a number of client systems, as shown in Figure 1.2. A server receives requests from these client
processes, and after suitably processing the request for appropriate business logic and data access
logic, the server process responds. In a more complicated environment, large enterprises could sup-
port many server systems connected to many client systems, in LAN/WAN/MAN scenarios.
Client/server architecture can be considered a paradigm change in the history of evolution of
information technology. Even in the present-day context, client/server concepts are very relevant
in understanding the business needs of enterprises.
he appearance of personal computers (PC) in the mid-1980s heralded a revolution in the
history of client/server architecture, as the low-cost PCs were quite attractive for SMBs as client
systems and minicomputers provided an excellent server medium for the client/server environ-
ment for these SMBs.
1.1.3 Distributed Computing Architecture
he distributed architectures enable multiple computers to be networked and services to be deployed
in a distributed fashion. hey are a natural and logical progression to client/server architectures.
hin Clients
Data Server
Application Server
Figure 1.2
Client/server architecture.
Search WWH ::




Custom Search