Server is a Network computer, computer program, or device that provides functionality for other programs or devices, called “client“.
This architecture is called the client-server model, and a single overall computation is distributed across multiple processes or devices On the world wide web. for example, a Web server is a computer that uses the HTTP protocol to send Web pages to a client’s computer when the client requests them. On a local area network, a print server manages one or more printers, and prints files sent to it by client computers. Network servers (which manage network traffic) and file servers (which store and retrieve files for clients) are two more examples of servers.. A single server can serve multiple clients, and a single client can use multiple servers. A client process may run on the same device or may connect over a network to a server on a different device. database servers, file servers , mail servers, print servers, web servers, game servers, and application servers.
Client–server systems are today most frequently implemented by (and often identified with) the request-response model: a client sends a request to the server, which performs some action and sends a response back to the client, typically with a result or acknowledgement. Designating a computer as “server-class hardware” implies that it is specialized for running servers on it. This often implies that it is more powerful and reliable than standard personal computer, but alternatively, large computing clusters may be composed of many relatively simple, replaceable server components.
In the beginning (well the 1980s), there were terminal servers. And they were good. These devices allowed for dozens of ‘dumb’ terminals to be connected to a mainframe or minicomputer over a single wired Ethernet connection. They were widely deployed at banks, automotive dealerships and insurance companies – anywhere a concentration of computer users was to be found. One of the main benefits was not having to run yet another cable all the way from the main computer to the new terminal location. As these terminal servers advanced, they allowed for another level of authentication to be implemented, via local username and password. Savvy administrators started finding ways to also connect printers to these server s and ultimately, terminal server designers added direct support for print queuing. This was a substantial timesaver, as now the printer could be placed near the user without a dedicated drop. Since some printers were installed remotely without associated terminals, it was a natural extension to create a terminal server dedicated to attaching printers to the network. With this, the print server was born.
In the late 1990s, web servers were added to device servers, giving them a new way of being configured and for data presentation. At this time, OEM manufacturers inquired about embedding device server functionality onto their main boards. Small products specifically designed for being embedded were created. These dispensed with the power supply regulation and serial interface circuitry. They were ideal for integrating to a main board, requiring only logic level power and signals. True to device server technology, they handled all of the tasks associated with getting a machine on to the network. It made networking easy for an OEM.
In 2002, Lantronix changed the face of embedded device servers when they came out with the ultra-miniature XPort. This was a complete serial-to-Ethernet device with web server in a standard sized RJ45 jack (about the size of two sugar cubes). Millions of these devices have been deployed worldwide.
You must be logged in to post a comment.