Overview#When speaking about Protocol interactions, the Protocol Server is the receiver with Protocol Client which must initiate the Protocol Exchange.
Example − Web Server (Protocol Server) keeps waiting for requests from Internet Browsers (Protocol Client) and as soon as it gets any request from a browser, it picks up a requested HTML page and sends it back to that Browser.
Note that the Protocol Client needs to know the address of the Protocol Server, but the Protocol Server does not need to know the address or even the existence of the Protocol Client prior to the connection being established. Once a connection is established, both sides can send and receive data using a protocol.RFC 2616 defines Protocol Server as service requests by sending back responses. Any given program may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as an Web Origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.