Hello Attila
Your description sounds just about right. Just a couple of comments.
- Your computer doesn’t create a pair of sockets, even though each communication has two sides to it. Your computer sees the socket as the IP address, transport layer protocol and port of the device it is connecting to. So the socket it sees is 157.240.22.35:80 using TCP. The web server sees the socket as 123.123.123.123:49152 using TCP.
- Secondly, when you go to Facebook, each click may be established using a different socket, or it may be part of the same socket. It depends on the way the web site is designed. Typically you will have several sockets created when communicating even with one web site.
- Finally, I keep using the word socket as you did as well, but we must keep in mind that this terminology has been largely replaced with the word “session.” So when using TCP, the word session is used to refer to each individual, independent communication that takes place using a particular socket.
Yes, that is correct. The session layer plays no role in this because when using TCP/IP there is no session layer. Above the transport layer we have the Application layer as seen here:
Great to hear that you are finding these conversations useful! It makes our job all the more rewarding.
I hope this has been helpful!
Laz
PS
I remember my first computer which had a 2400 baud modem with WIndows 3.1, we’d use a software utility called Winsock which would create this socket with an Internet provider’s server to gain access to the Internet. Those were the days… 