02.2 (Conspect) Sockets

We continued the last lecture about the global network.

Global network

The task of data transfer is solved, but:

So we shall continue. Next subtask is to unite all local networks (sets of nodes bound by joint media) into global network

Router
a node of two or more local networks, that can retransmit packets from one network to another
Route
a chain of routers leads from sender to recipient
Routing

a process of determining this chain

Host
a node of global network

Identifying and routing

Dynamic connectivity

No host can bear a full routing map of global network:

But some information on what is connected to what is critical. Question is: what is «what»?

E. g.: the Internet

Sockets

Socket
universal, asynchronous data transfer process. Looks like a portal - we shove data into one receiving hole and it falls out of the other end of the hole. And this data can be in the system. Or these holes are abstract - we create some kind of descriptor. Socket - socket - name of the program interface to provide data exchange between processes. Processes during this exchange can be executed on one computer or on different computers connected by a network. Socket - abstract object representing an endpoint of connection. A socket is much more universal abstraction. Visualization can be nailed to different family of protocols (network). Socket documentation describes a huge number of protocol families. It means that when we create a socket we create some interface between the 4 transport layer and the 3 delivery layer.
TSP
streaming connection, here we are guaranteed overfill protection. If on one side (A) the computer tries to transmit data very quickly, and on the other side (B) the computer receives it very slowly or there is a narrow channel in the middle which routes it very slowly.

HSE/ArchitectureOS/02_SocketProgramming/Conspect_en (последним исправлял пользователь NataliaKrauze 2020-04-17 17:53:37)