Server and Client

The two processes that communicate through a logon TCP have various roles:

* The process that starts one new logon TCP is said client, and sendes one demanded of logon towards one determined door.
* So that the logon comes established, on that door must is to us a serveur process "in listens", than chip ax to establish one logon TCP.

The known and recorded doors therefore are used from the serveur processes, and conventionally are associated to particular services, so that a client it knows which door to connect itself in order to catch up a determined serveur.

The serveur process, that it is in I listen on a sure door, remains blocked in attended that a client it is connected. The process client demands to establish one logon towards a determined serveur on one determined door. Normally the door source used from the client comes allotted dynamically from the operating system of the client. When the TCP establishes the logon, to both processes it comes assigned a socket through which they they can communicate between they. Typically the serveur process carries out a fork, entrusts to the son the task to communicate with the new one client and it recovers in I listen. From this point in then, client and serveur they have symmetrical roles, and they use the same instruments in order to communicate through the socket.