client-server system | multiple threads of control that can be concurrently executed to implement concurrent operations, otherwise when the client is waiting for one kind of input, it will not be able to respond to the other kind of input | clients and servers | which is then implemented by a collection of components | developers of clients are frequently forced to upgrade their clients whenever the server is changed if clients and servers are developed by different organizations | at least one server and one client | forward-compatible and backward-compatible with other versions of clients and servers by designing the client-server protocols to be very general and flexible | even if its components change over the course of time, or are replaced by equivalent components | subsystem | 3.4 - The Client-Server Architecture | encryption, firewalls and similar methods of ensuring security | - The server starts running
- The server listens for clients wanting to connect
- Clients start running and perform various operations, some of which require connecting to the server to request a service
- When a client attempts to connect, the server accepts the connection if it is willing
- The server waits for messages to arrive from connected clients
- When a message from a client arrives, the server takes some action in response, such as sending a message back to the client, then resumes waiting
- Clients and servers continue functioning in this manner until one of them decides to shut down
| distributed system | |