Group: file system
Topic: communication port
Topic: communication protocols
Topic: file input/output
Topic: implementing distributed systems and applications
Topic: interprocess communication
Topic: Internet
Topic: locating named objects by broadcast
Topic: message queues for communication
Topic: name server or name directory
Topic: remote procedure call
Topic: open systems
Topic: specification and design of distributed systems
Topic: system integration
| |
Summary
The client-server model is a standard model for distrubuted systems. One computer, the server, implements a service that processes requests from its clients. For example a file server delivers files on request.
Service discovery can be difficult in large, public systems. Other issues include authentication, security, quality of service.
Client-servers are typically implemented with message passing, defined by a communication protocol. (cbb 8/06)
Subtopic: client-server
Quote: implement distributed systems via servers and clients on a local area network; clients request services from servers [»shriS7_1982]
| Quote: large, distributed system by a small set of physically distinct servers that change slowly and a large set of clients [»satyM1_1992]
| Quote: design distributed system as services offered by servers and negotiated by clients; only need to specify communication [»cherDR4_1984]
| Quote: Amoeba objects are abstract data types managed by server processes
| Quote: with a workstation per user have a very low average load; no need for computation servers
| Subtopic: loosely coupled
Quote: servers should run asynchronously with respect to clients; loosely coupled, maximize throughput, prioritize requests, failover [»boswA10_2005]
| Quote: an XML schema is a shared secret that ties clients and servers together
| Subtopic: service discovery
Quote: logical identification of clients and servers does not scale to thousands of sites
| Quote: a Jini server responds to requests with a proxy for interacting with the server; the Java type defines its interface
| Quote: a Pilot server listens for requests on an advertised network address; new network streams are assigned to a different network address [»redeDD2_1980]
| Subtopic: service assignment
Quote: a Jini component offers a resource via a lease for a specific period of time; may be cancelled by client or renewed by client and server [»waldJ7_1999]
| Subtopic: protocols
Quote: client/servers need protocols for naming, objects, operations, and transport-level data communication [»cherDR4_1984]
| Quote: all client/server communication via V kernel IPC facilities; for protection and autonomy [»cherDR4_1984]
| Quote: Clearinghouse clients are machines so all interaction must be automated [»oppeDC7_1983]
| Subtopic: message passing
Quote: a V server can process messages in any order; for scheduling flexibility
| Quote: handle concurrency with a manager process that only receives and replies to messages, and several helper processes [»liskB10_1981]
| Quote: in a message-passing system, the sender can use procedure call semantics while the receiver use message queue semantics [»liskB10_1981]
| Subtopic: file server
Quote: a Coda open yields the most recent server copy or a cached copy; if no server on close then queues update [»satyM4_1990]
| Quote: volumes needed for managing large distributed file systems; i.e., part of a single disk partition that is associated with a user [»howaJH2_1988]
| Quote: a filing system is a client of the backing store server; applications have access to either [»birrAD9_1980]
| Quote: a file server stores and retrieves bulk data for a local area network [»birrAD9_1980]
| Quote: each major client of a file server needs a charging capability to account for file creation and storage [»birrAD9_1980]
| Subtopic: authentication server
Quote: an authentication server can act like a notary public; validation of public keys is a natural extension of its public key service [»bootKS11_1981]
| Quote: a Helix client collects a set of capabilities needed for a user session [»fridM5_1985]
| Subtopic: server capacity
Quote: web servers normally handle 100 requests a second within an order of magnitude [»boswA10_2005]
|
Related Topics
Group: file system (9 topics, 305 quotes)
Topic: communication port (40 items)
Topic: communication protocols (62 items)
Topic: file input/output (21 items)
Topic: implementing distributed systems and applications (41 items)
Topic: interprocess communication (29 items)
Topic: Internet (16 items)
Topic: locating named objects by broadcast (9 items)
Topic: message queues for communication (36 items)
Topic: name server or name directory (40 items)
Topic: remote procedure call (44 items)
Topic: open systems (33 items)
Topic: specification and design of distributed systems (14 items)
Topic: system integration (5 items)
|