Client is a computer that gets information from another computer called server in the context of client–server model of computer networks.[1] The server is often (but not always) on another computer system, in which case the client accesses the service by way of a network.[2]
A client is a computer or a program that, as part of its operation, relies on sending a request to another program or a computer hardware or software that accesses a service made available by a server (which may or may not be located on another computer).[3] For example, web browsers are clients that connect to web servers and retrieve web pages for display.[3] Email clients retrieve email from mail servers. Online chat uses a variety of clients, which vary on the chat protocol being used. Multiplayer video games or online video games may run as a client on each computer.[3] The term "client" may also be applied to computers or devices that run the client software or users that use the client software.
A client is part of a client–server model, which is still used today. Clients and servers may be computer programs run on the same machine and connect via inter-process communication techniques. Combined with Internet sockets, programs may connect to a service operating on a possibly remote system through the Internet protocol suite. Servers wait for potential clients to initiate connections that they may accept.
The term was first applied to devices that were not capable of running their own stand-alone programs, but could interact with remote computers via a network. These computer terminals were clients of the time-sharing mainframe computer.
Types
editRelies on local storage |
Relies on local CPU | |
---|---|---|
Fat client | Yes | Yes |
Diskless node | No | Yes |
Thin client | No | No |
In one classification, client computers and devices are either thick clients, thin clients, or diskless nodes.
Thick
editA thick client, also known as a rich client or fat client, is a client that performs the bulk of any data processing operations itself, and does not necessarily rely on the server. The personal computer is a common example of a fat client, because of its relatively large set of features and capabilities and its light reliance upon a server. For example, a computer running an art program (such as Krita or Sketchup) that ultimately shares the result of its work on a network is a thick client. A computer that runs almost entirely as a standalone machine save to send or receive files via a network is by a standard called a workstation.
Thin
editA thin client is a minimal sort of client. Thin clients use the resources of the host computer. A thin client generally only presents processed data provided by an application server, which performs the bulk of any required data processing. A device using web application (such as Office Web Apps) is a thin client.[4]
Diskless node
editA diskless node is a mixture of the above two client models. Similar to a fat client, it processes locally, but relies on the server for storing persistent data. This approach offers features from both the fat client (multimedia support, high performance) and the thin client (high manageability, flexibility). A device running an online version of the video game Diablo III is an example of diskless node.
References
edit- ^ "1.1.2.2 Clients and Servers". Cisco Networking Academy. Retrieved 2024-04-07.
Servers are hosts that have software installed that enable them to provide information...Clients are computer hosts that have software installed that enable them to request and display the information obtained from the server.
- ^ Course, Microsoft Official Academic (8 July 2008). Exam 70-643 Windows Server 2008 Applications Infrastructure Configuration. John Wiley & Sons. ISBN 978-0-470-22513-4.
- ^ a b c "client/server". PCMag Encyclopedia. Retrieved 8 November 2022.
- ^ Baratto, Ricardo A.; Kim, Leonard N.; Nieh, Jason (20 October 2005). "THINC: A virtual display architecture for thin-client computing". Proceedings of the twentieth ACM symposium on Operating systems principles. Sosp '05. Association for Computing Machinery. pp. 277–290. doi:10.1145/1095810.1095837. ISBN 9781595930798. S2CID 723321.