A network architecture in which each computer or processor on the network is either a Client or a Server. Servers are powerful computers or processors dedicated to managing disk drives (file servers), printers (print servers) or network traffic (network servers). Clients are PCs or Workstations on which users run applications. Clients rely on servers for resources such as files, devices and even processing power. Client-server architectures are sometime called two-tier architectures.
A network architecture in which each computer or process on the network is either a client or a server. Servers are powerful computers or processes dedicated to managing disk drives (file servers), printers (print servers), or network traffic (network). Clients are desktop computers (such as Macintoshes, PCs, or workstations) on which people run applications. Clients rely on servers for resources, such as files, devices, and even processing power.
In a LAN where computers are either servers or clients. Clients depend on the server. The server is usually a much more powerful computer.
The structure of Web technology, consisting of two parts: a client and a server. The server is where information that a user accesses is stored; the client is software that enables a user to access the information.
A basic concept used in computer networking, wherein servers retrieve information requested by clients, and clients display that information to the user.
Client-server architecture is a distributed system in which several clients and at least one server, cooperate based on the division of labor. In a client-server network a server (at least one) provides data and services (for instance mail exchange or providing data) to the client. The server accepts the clients' requests and sends the requested data over the network. The Internet represents a typical client-server system, where clients communicate with the web server via the TCP/IP protocol.
A computer network that is made up of client computers and server computers.
An information-passing scheme that works as follows: a client program, such as Mosaic, sends a request to a server. The server takes the request, disconnects from the client and processes the request. When the request is processed, the server reconnects to the client program and the information is transferred to the client. This architecture differs from traditional Internet databases where the client connects to the server and runs the program from the remote site. Note: in an X-11 environment, the meanings of client and server are reversed.
A way of enabling the computing load to be distributed among many clients, as well as the server that holds the information.
A computer network architecture that places commonly used resources on centrally accessible server computers, which can be retrieved as they are needed across the network by client computers on the network. See also: Client, Server.
A system in which databases reside on a server (i.e., a networked microprocessor-based host) that handles the bulk of the processing. The client (i.e. a desktop computer) provides the user interface but does little of the processing.
A catchall term used to refer to a distributed environment in which one program can initiate a session and another program answers its requests. The origin of client-server designs is closely allied with the TCP/IP protocol suite.
The underlying philosophy of centralized processing. In multiple computer systems it can be more efficient for only one computer (the server) to perform certain operations. When another computer requires the data, no processing or synchronization is required, the data is merely requested from the server.
An application architecture where one end system (the client) requests another end system (the server) to perform operations and to giveback results.
Software architecture based on a separation of processing between two CPUs, one acting as the client in the transaction, requesting and receiving services, and the other as the server that provides services in a transaction.