Server and Client

Basically if we talk about the Server and Client, most of us think that it is more complex terms. But in fact, it is easier to understand what is server and what is client? The thing we should know for server is that it is the system that serves us.Server in easier words, is the computer that provides us the internet facility. In our general cases, if we goto cyber cafe, the main computer in front of the cyber is Server and the computer that gets the facility from the sever is the Client. Its like going to the restaurant. In the restaurant the waiter acts like server . The waiter comes through the menu. It is like you send the request. And finally the waiter comes with the items that you requested to him.
I guess that you somewhat extent got the knowledge of server and client.

In our daily life, in the internet, we usually send the request to servers and servers provides us the information about the page. This is how the server and client works. The only data we get is the reply from the server. If the server is not responding that means the server is not getting the request that client sends.

For example, a server machine might have software running on it that allows it to act as a Web server, an e-mail server and an FTP server. Clients that come to a server machine do so with a specific intent, so clients direct their requests to a specific software server running on the overall server machine. For example, if you are running a Web browser on your machine, it will most likely want to talk to the Web server on the server machine. Your Telnet application will want to talk to the Telnet server, your e-mail application will talk to the e-mail server, and so on…

The client’s responsibility is usually to:

1. Handle the user interface.
2. Translate the user’s request into the desired protocol.
3. Send the request to the server.
4. Wait for the server’s response.
5. Translate the response into “human-readable” results.
6. Present the results to the user.

The server’s functions include:

1. Listen for a client’s query.
2. Process that query.
3. Return the results back to the client.

 The architect of typical client/server interaction goes like this:

1. The user runs client software to create a query.
2. The client connects to the server.
3. The client sends the query to the server.
4. The server analyzes the query.
5. The server computes the results of the query.
6. The server sends the results to the client.
7. The client presents the results to the user.
8. Repeat as necessary.

Happy socket coding…….