Professional Documents
Culture Documents
Client Server Technology
Client Server Technology
Client Server Technology
1.Abstract
2. Client Sever Architecture
2.1 Evolution
2.2 Evolution of Architectures:
2.2.1 Mainframe architecture
2.2.2 File sharing architecture:
2.2.3 Client/server architecture:
2.3 Client Server Architecture Models:
2.3.1 FAT Vs THIN
2.3.2Two-tier and Three-tier Architectures:
2.4 Characteristics
2.5 General Issues in client-server computing
3. Distributed System Architecture
3.1 Remote Procedure Call (RPC):
3.2 Object Management Architecture (OMA):
3.3 Distributed Resource Architecture:
3.3.1. Distributed data Architecture:
3.3.2 Distributed Server Architecture:
3.3.3 Distributed Computing Architecture:
4. Distributed Architecture Requirements
5. Conclusions
6. Bibliography
1. ABSTRACT
2.1 Evolution:
The term client/server was first used in the 1980s in reference to
personal computers (PCs) on a network. The actual client/server model
started gaining acceptance in the late 1980s. The client/server software
architecture is a versatile, message-based and modular infrastructure that is
intended to improve usability, flexibility, interoperability, and scalability as
compared to centralized, mainframe, time sharing computing.
2.4 Characteristics
Client/server is a software model of computing, not a hardware
definition. Because the client/server environment is typically heterogeneous,
the hardware platform and operating system of the client and server are not
usually the same. In such cases, the communications mechanism may be
further extended through a well-defined set of standard application program
interfaces (APIs) and remote procedure calls (RPCs). This architecture has
the following characteristics.
In any system two aspects may be distributed, these are a.) Components of
the application running on the system and b.) System resources, thus
client/server technology becomes a general case of (a) which may be
rephrased as distributed component computing or as distributed object
computing. Which are basically client/server models with middleware the
various types of middleware are:
The various OMA Modules that may be identified from the above diagram are
Object Request Broker: directs requests and answers between objects
Object Services: basic functions for object management (e.g., name service)
Common Facilities: generic object-oriented tools for various applications (e.g.,
a class browser)
Application Objects: classes specific to an application domain (e.g., a CASE
tool)
Here we may define an object and a request as follows:
An object is an abstraction with a state and a set of operations
A request is an operation call with one or more parameters, any of which may
identify an object (multi-targeting); Arguments and results are passed by
value.
The following are the features of CORBA
• Communications substrate
• A specific programmer interface (no implementation)
• Multi-vendor ORBs to interoperate (CORBA-2)
• Layered on top of other communication substrates (RPC, byte streams,
IPC,…)
• Language mapping (C, C++, Ada, Smalltalk, Java,Cobol)
• ORB interface.
3.3 Distributed Resource Architecture:
The term distributed can be applied to any resource that can be shared.,
this includes data, services, hardware, computing power. Thus there are 3
types of distributed architectures.
1. Distributed data architecture
2. Distributed Server architecture
3. Distributed computing architecture
5. CONCLUSION