Ports vs Sockets

[ChristianSparks]

Okay, correct me if you think I am incorrect, but your video made me think about ports and sockets through an analogy. To set the proverbial stage, an IP Address is a phone number of a particular hotel. Ports are rooms with numbers wth possible occupants. An application is an occupant. Sockets are different phone extension numbers to each room.


With the stage set, let us begin the proverbial play. An Application (occupant) in a particular hotel room (port) at a different hotel/phone number (IP Address) places a call (TCP/IP and UDP/IP.) to another hotel/phone number (IP Address) to a particular hotel room (port), where an occupant (application) answers the phone (socket), and begins communicating (acknowledging TCP/I or UDP/IP) . During the phone call between the occupants (application) they exchange information (TCP and UDP Packets). Furthermore, a conference call (TCP/IP and UDP/IP) can be initiated between adjoining rooms (ports) occupied by the same occupant (application) using different phones (sockets) in each of the rooms (ports). Once the phone call is complete, the occupants (application) signal completion of the phone call (TCP and UDP Packets transmission) and hang up the phone (terminate the socket) between the rooms (ports).


Would you let me know if I am in the ballpark?

[ericmosbaugh]

I rather like that you kept rolling on a few topics here. Great video. Five min info videos are often a waste of time.

[gladwinrojer]

So, we should only talk about SOCKETS when we actually implement networking in a programming CODE.

In theory, it is only the ip address and the port number that matters.

I always had this doubt like when there is only ip address and port numbers are needed to identify a process in a target system, why is there a new term called this video is really an eye talk sockets only in the programming code as socket(ip_address, port_num)

[INTJames]

wouldnt the stdin label on the second arrow coming out of process one's 1 stdout stream be labeled stdout? "1>filename" would send stdout to a file, plus the arrow is pointing to the file, and coming from the number 1, which is stdout