CLIENT SERVER

BUILDING BLOCKS
 Architecture

• Identifies structural elements in the construction of systems (houses,

high rises, office buildings, and cities etc…)
• Determines the structure and shape of the client/server systems we
can build to meet various needs.
 Topics to be covered
• How is the application split between client and server?
• What function goes in client and in server?
• Can the client server model accommodate businesses of all size?
• Can client/server plays in home?
and so on….
CLIENT/SERVER :A one-size-fits-all model

• Simple, works well with today`s technologies.

• 3 building blocks
• Client
• Server
• / -> ties client to server.
How the building blocks are
used in various situations?
• Client/Server for tiny shops and nomadic tribes.
• Client/Server for small shops and departments.
• Client/Server for intergalactic enterprises.
• Client/Server for a post-scarcity world.
Client/Server for tiny shops and nomadic tribes.

• Client, middleware software and most of the business services runs

on the same machine.
• Easy to run and manage both of them on the same machine.
• Sometimes it does communication with outside servers to exchange
data, refresh database, send or receive mail.

• Problem: Operating System must be robust enough to run both client

and server sides of application.

• Example: one person shop, home office, and mobile users.

 Client /server for tiny shops and nomadic
users.
Client/Server for small shops and
departments
• Classic Ethernet Client/Server building-block implementation.
• LAN based single server establishment.
• Multiple clients talks to a single server.
• Simple middleware.
• Client needs to look into the configuration file to find its server name.
• Security, network administration is simple, failure (in client/ Server).
• Communication with other server possible.
• Examples: Small shops, departments and branch offices.
Client/Server for small shops and departments
Client/Server for intergalactic
enterprises.
• Addresses the needs of heterogeneous servers.
• Vertically scalable.
• For the need of more processing power in intergalactic function, more
servers can be added, or existing server machine can be upgraded.
• The servers can be partitioned based on the functions they provide,
the resource they control, or the database they own.

• Advantages multiserver capability:

High computation power and flexibility
• To exploit the full powers of multi server, the following needs
• Low-cost, high –speed bandwidth

• Awesome amount of middlewares

• It also includes network directory services, network security, rpc, network

time services
• It creates a common view of all the services on the network, called “Single
system image”.
Client/Server for intergalactic
enterprises.

Single
system
image
• Every machine is both a client and a server –post scarcity world.
Inside the building block
• Building Blocks:

• Client
• Server
• Middleware

• What does go in the building blocks?

Client building blocks

• Runs client side of the application.

• Runs on OS and provides GUI/OOUI(Object Oriented User Interface).
• DSM component ( Distributed System Management )
- Anything from a simple agent on PC to the entire front-end of the DSM
application on a managing station.
Server building block
• Runs server side of the application.
• 5 server platforms
• SQL database server
• TP monitors
• Groupware servers
• Object servers
• Web
• It depends on OS to interface with middleware.
• DSM component ( Distributed System Management )
- Anything from a simple agent on PC to the entire back-end of the DSM application on a
managing station.
Middleware
• Runs both on Client and Server sides of the application.
• Nervous System.
• It covers all the distributed software needed to support interactions
between client and server.
• Software that sits between the client-side request on the front end
and the back-end resource being requested.
• 3 categories
• Transport stack
• Network Operating System(NOSs)
• Server specific middleware.

• DSM component exists.

• DSM

• Runs on every node in Client/Server network.

• Managing workstation - Collects information from all
agents on the network and displays graphically.
• It instructs its agents to perform actions on its behalf.
Server to Server middleware
• Middleware:

• Doesn`t include any software that provides the actual service.

• Includes the software that coordinates inter-server interactions.

• Server to server interaction

• client to server in nature
• Some requires specialized server middleware.
• Example:- server on mail backbone uses special server to server middleware
for doing store and forward type messaging.
CLIENTS,SERVERS,AND
OPERATING SYSTEM
-Brief description about client server needs from os.
 Anatomy of a server program
• Role of server – to serve multiple clients.

• It does
• Waits for client – initiated requests
-Dedicated /dynamic pool of reusable sessions
• Executes many requests at the same time
• Takes care of VIP clients first.
- Provides multiple level of priority to its clients.
• Initiates and runs background – task activity.
• Keeps running.
-Robust (if server down – impact reflected)
• Grows bigger and faster.
What does a server needs from
an OS?
• OS function
• Base
• extended service.
• Base Service
• standard OS
• Extended Service
• Add-on modular software component
• Layered on base service.
Base Service
• Servers has high level of concurrency.
• Multitasking environment – Task management
• Improves
• Performance
• Throughput
• Modularity
• Responsiveness of the server programs.
Server Requirements from OS
• Task preemption
• Task priority
• Semaphores
• IPC
• Local/Remote IPC
• Threads
• Intertask protection
• Multiuser high-performance
• Efficient memory management
• Dynamically linked run-time extensions
Extended Services
• Provides advanced system software

• Distributed potential of networks

• Flexible access to shared information
• System management and maintenance easy
• ISVs (independent software vendors) and system integrators –
create new server applications.
Expectations from extended server
• Ubiquitous communications
• Rich set of communication protocol stack – enables server to communicate
with greatest number of clients and other servers.

• Network Operating Systems Extensions

• Must provide extending the file and print services over network.
• Access to any remote device.
• Example : printers, file as if they are local
• Binary Large Objects (BLOBs)

• Images, videos, graphics, intelligent documents, and database

snapshots ------> large objects
• OS requires extensions such as intelligent message streams and
object representation format.
• Network must move and transport it at high speeds.
• Database and file systems must store and access it.
• Protocols are needed to exchange them across systems and for
associating them with programs that know what to do when they
seen.
• Global directories and Network yellow pages

• Clients must locate servers ad their services on network using a

global directory service.
• Network resources must be found by name.
• Dynamic registration with provider.

• Authentication
• clients must prove to server

• Authorization services
• Verifies whether the authenticated client has permission to
obtain a remote service
• System management

• Integrated network and system management platform

• Can act as single/multiple servers.
• System management includes
• configuring a system,
• monitoring the performance of all elements,
• generating alerts,
• distributing and managing the software packages on client
workstations,
• checking for virus and intruders
• metering capabilities.
• Network Time
• Client and server clock synchronization
• Time – coordinated with universal time authority.

• Database and Transaction services

• Robust multiuser DBMS
• DBMS must support
• SQL for decision support
• Server stored procedures for transaction services
• Created outside the OS
• Managed by TPMonitor
• Internet services
• Common internet services becomes as standard server features.
• Example – HTTP daemons, SSL, firewalls, DNS, HTML based file
systems, e-commerce frameworks.
• Object-oriented services
• Services – object oriented
• object broker services – allows object interaction across the
network.
• Object interchange services and object repositories.

Standardize a multiplatform set of

extended services---Middleware
Server Scalability
Compound Documents : OOUI on
steroids
• Compound Document framework - ActiveX and java Beans – OOUI
technology
• Visual object - component
• Embedding components – containers.
• component – independent piece of software that can be purchased I
market.
• Rectangular or in any shape, moved around, embedded, resized.
• Like simulation.
• 3-D compound documents – too realistic simulation.
Shippable places
• Place
• visual ensemble of related components.
• Shippable place – mobile container of components (i,.e.,
shipped over net)
• Mini virtual world.
• Allows servers to automatically update the desktop.
• Dynamic assembly of ever changing data, video feeds, and
other live content.
Client/Server hybrids
• Industries moves beyond pure client/server model.
• Server lite function
• full client and server function on every machine.
• Provides a thread, queue or background process on the client machine.
• Clients with server lite function – hybrids.
 The OS wars : Meet the players

• Picking Client/Server platform is not easy.

Client OS trends
• The desktop is becoming more fragmented.
• The universal client is really a web browser.
• There will be a huge demand for super-fat PC`s
• There will be a huge demand for ultra-thin PC`s.
• Shippable places will become the new desktops.
• Embedded clients will be everywhere.
Client OS : Meet the players
Client OS: Meet the players
• Client platforms
• Most – Microsoft
• Next-Mac OS and Linux
• JAVA OS –formidable competitor (Internet applications)
NT Client
• Windows NT Workstation

• Robust 32-bit client OS.

• Supports preemptive multitasking, multithreading, memory
protection and transactional file system.
• Network- ready
• supports TCP/IP, NetBEUI, IPX/SPX, PPP and AppleTalk.
• Provides C2-level security.
NT Client (contd..)
• Cons comparing with windows

• Resource hog
• Support for laptop – poor (limited PC card support and power
management).
• Poor emulation of DOS and 16-bit applications.
• Doesn`t support plug and play.
• Limited device driver support.
• Expensive.
• Windows 98 to 2000 (Microsoft adds conversion features in NT 5.0).
Mac OS X
• Key player on the desktop.
• Combination of Mac OS 8.5 and NeXT`s OpenStep 4.2
• It can run openstep applications and mac applications also.
• Inherits from NeXT and BSD 4.4 Unix layer.
• Provides protection, threading, preemptive multitasking.
• Supports JAVA.
Mac OS X (Contd..)
• Cons
• Requires new device drivers for most third party hardware.
• Integration of different application personalities to provide a seamless Mac
look and feel.
Linux
• Ran mostly on servers.
• “Free Unix” that uses with Apache web servers.
• Linux is one of the fastest – growing client operating system. (Moving
to client side)
• Linux is the most reliable version of Unix running on Intel.
• Apps:
• Intel based Unix application runs on Linux without modifications.
Linux ( contd…)
• Example : staroffice, Applix-ware.
• Support : Excellent free support.
• Cons :
• Doesn`t run windows applications (Microsoft Office).
• Doesn`t provide a single desktop environment.
• For sale vendors provides very useful service, but they may also
end up splintering the Linux community.
SERVER OS:MEET THE PLAYERS
• Low to medium end of the server market
• NetWare, OS/2 Warp server, NT server, Unix

• High end
• Unix clusters and to any mainframe or supermini.
Server OS : Meet the players
• NetWare
• Developed by novel
• Very fast, effective, well – supported file server
• Supports OS/2,Mac and Window clients.
• Includes X.500 ( Global directory service) and necessary tools.
• Has large support and sales infrastructure
• Introduced Intranetware, provides a built-in web server.
NetWare (contd..)
• Good news about Netware 5.0

• Fixes all problems of Netware 4.X

• Supports SMP, preemptive multitasking, virtual memory management
• Support for pure IP (no more tunneling of IPX inside IP packets).
• Provides fastest and more secure Java VM`s
• Support for EJB and CORBA/IIOP. It helps to create server-side beans on the
NetWare platform.
NetWare (contd..)
Cons of Netware 4.X
1. Netware 4.X poor application server.
• NLM`s – Netware Loadable Modules
• Special namespaces set aside on the server that let programmers provide new system
services.
• Problems in NLM to use Netware 4.X as general purpose, modern, application server
platform.
• Limited memory protection
• Lack of memory management (no virtual memory)
• No support for preemptive multitasking.
2. Too closely tied to a proprietary networking protocol (IPX/SPX)
3. It doesn`t take full advantage of SMP.
4. It doesn`t provide an integrated suite of back-end applications.
NT Server
• Features of NT Server over workstation.
• File/print server support
• Built-in internet server
• Disk mirroring
• Striping
• SMP
• It is a Good application, database and file/print server platform.
• Cons
• No scalability
• No enterprise directory server
• security issues
NetWare (contd..)
• All the products of Netware 5.0 are directory-enabled and have
common administration facilities.
• It includes Netscape`s FastTrack Server, a five-user version of the
Oracle 8, a certificate server, and Z.E.N works.
• Modesto product – 64-bit version of Netware for Merced chip.
• It provides advanced clustering support.
OS/2 Warp server
• Excellent application server.
• In 1996 ->Warp server released
• LAN Server
• Above both combined as OS/2 Warp server
• It provides
• Disk mirroring
• Remote administration
• Remote software distribution
• A backup server
• Software metering
UNIX
• Function rich os
• Scalable from desktop to supercomputer.
• Latest growth ->internet (mail, FTP, TCP/IP, DNS)
• Introduces JAVA and CORBA

• Cons
• Which UNIX to choose?
• Server scalability suffers from
• Lack of binary compatibility
• Functional differences among the Unixes