{"id":164,"date":"2020-11-28T10:09:25","date_gmt":"2020-11-28T15:09:25","guid":{"rendered":"https:\/\/www.alpharithms.com\/?p=164"},"modified":"2021-07-20T22:45:11","modified_gmt":"2021-07-21T02:45:11","slug":"network-sockets","status":"publish","type":"post","link":"https:\/\/www.alpharithms.com\/network-sockets-250910\/","title":{"rendered":"Network Sockets: The Bridges Between End Systems"},"content":{"rendered":"

Network Sockets (a.k.a.\u00a0Internet<\/em>\u00a0Sockets<\/em>) are application-level software implementations that map data from a process on one network machine to another network machine. They were originally defined in the 1971 RFC 147 to describe network communication within the ARPA network (R<\/a>).<\/p>\n

Sockets are essential to network communications but sometimes get discussed such that lead to unclear definitions. At their core, sockets are software-level implementations that serve as connections between processes on different network end systems. Another way to define sockets is as a process interface<\/strong> through which data are sent and received.<\/p>\n

Overview<\/h2>\n

Technical implementations of sockets have evolved greatly since their early inception. Initially, a\u00a0Network Socket<\/em> was defined as such:<\/p>\n

… the unique identification to or from which information is transmitted in the network. The socket is specified as a 32-bit\u00a0number with even sockets identifying receiving sockets and odd sockets identifying sending sockets. A socket is also identified by the host in which the sending or receiving processer is located.<\/em><\/p>\n

Conceptually, network sockets serve as bridges between network applications such that information from a sender can arrive safely at a receiver. In many modern networked applications, the sender\/receiver relationship can be described as client\/server where a\u00a0server socket<\/em> is established and “listens” for incoming client socket<\/em> connections.\u00a0 Beyond this conceptual distinction, network sockets can be categorized by several technical means as well.<\/p>\n

What is a Socket, really<\/em>?<\/h2>\n

As a simple concept, sockets can be thought of as transport-layer facilitated connections between end systems; bridges between river banks. In more technical terminology; sockets are endpoint\u00a0instances<\/em> within a network such that physical end systems can maintain multiple sockets to multiple other end systems.<\/p>\n

Host Address + Port Number<\/h3>\n

A host address is, ultimately, a machine-friendly identifier that helps one end system locate another end system within a networked environment. Common host addresses take human-friendly formats such as www.example.com but are translated to machine-readable IP addresses by domain name service (DNS)<\/a> protocols.<\/p>\n

Ports are locational constructs that allow different processes to communicate. Ports are software-based (there are no physical layer ports) that are managed by a computer’s operating system. In the context of networking, ports identifiers used to locate a process on a local machine such that a remote machine can connect accordingly. Getting the bits to the right neighborhood\u00a0and<\/em> to the right house, as it were.<\/p>\n

The combination of host:port<\/code> addressing helps a process on one machine connect to another machine and locate a corresponding process there. The initial specification for TCP refers to a specific host:port<\/code> address as an\u00a0end system<\/em> and sometimes refers to that construct as a socket (R<\/a>). This builds to define a TCP connection<\/em> as two sockets<\/em>.<\/p>\n

Types of Network Sockets<\/h2>\n
\"network
Network sockets facilitate the transmission of application-layer data between networked devices.<\/figcaption><\/figure>\n

There are several types of network sockets available, though Stream Sockets and Datagram Sockets are the most popular. These types of network sockets support TCP and UDP communications; the two most implemented transport-level protocols among Internet applications (R<\/a>).<\/p>\n

Stream Socket<\/h3>\n

Stream sockets are used with Transmission Control Protocol (TCP) applications or Stream Control Transmission Protocols (SCTP) and support the Reliable Data Protocols (RDP) inherent to each.<\/p>\n

Datagram Socket<\/h3>\n

Datagram sockets are used to support User Datagram Protocol (UDP) applications that rely on connectionless data transfer. Each packet sent via datagram sockets is individually addressed and routed but takes no measure to ensure order or arrival. Datagram sockets are considered to be “unreliable” transport services.<\/p>\n

Raw Socket<\/h3>\n

Raw sockets allow the send\/receive of Internet Protocol packets from the network layer without any specific constraint on protocol (TCP, UDP, etc.). As such, header specifications are made at the application layer when sending and much of the encapsulation is left up to application developers.<\/p>\n

Client Sockets vs. Server Sockets<\/h2>\n

In Internet Protocol (IP) there is no generic difference between a client socket and a server socket. Both are implemented to map a process on one network machine to a process on another network machine. On an application level, however, these types of network sockets can be distinguished as such:<\/p>\n

Client Socket<\/strong> – Created to send a connection request to a specific host:port<\/code> combination. Waits in the server-side connection queue until accepted.<\/p>\n

Server Socket<\/strong> – Created to\u00a0listen<\/em> for incoming client connection requests on a specific port on a given host. Created on well-known ports mapped for connections of a particular protocol. Port 80<\/code> for HTTP requests, for example.<\/p>\n

Socket Protocols<\/h2>\n

In addition to sockets being configurable to different ports, they too can be configurable for different transport-layer protocols such as TCP or UDP. The nature of TCP and UDP help define the differences in socket type:<\/p>\n

UDP Socket<\/strong> – Uses a two-tuple {host:port}<\/code> set for only the destination address.<\/p>\n

TCP Socket<\/strong> – Uses a four-tuple {source:port, host:port}<\/code> set for host and destination addresses.<\/p>\n

UDP is a connectionless protocol that makes no affordance to data reliability. As such, there is no need for a “return address” because the recipient makes no effort to make acknowledgment to the sender.<\/p>\n

TCP is a connection-oriented protocol<\/a> that makes certain guarantees for data arriving in order, without loss, and keeping network congestion to a minimum. As such, TCP needs to facilitate full-duplex communication. Knowing both the sender and receiver addresses are required for this.<\/p>\n

Review<\/h2>\n

If you’d made it this far you’re likely now aware that the term\u00a0socket<\/em> is fairly abstract. On one hand, it’s a very concrete construct that connects two network end systems. On the other, different ports can be used to create many virtual endpoints on a single host system. The more easily-defined attributes of sockets are that they require host:<\/p>\n","protected":false},"excerpt":{"rendered":"

Network Sockets (a.k.a.\u00a0Internet\u00a0Sockets) are application-level software implementations that map data from a process on one network machine to another network machine. They were originally defined in the 1971 RFC 147 to describe network communication within the ARPA network (R). Sockets are essential to network communications but sometimes get discussed such that lead to unclear definitions. […]<\/p>\n","protected":false},"author":2,"featured_media":167,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[3],"tags":[78,6,83],"acf":[],"_links":{"self":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts\/164"}],"collection":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/comments?post=164"}],"version-history":[{"count":5,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts\/164\/revisions"}],"predecessor-version":[{"id":233,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts\/164\/revisions\/233"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/media\/167"}],"wp:attachment":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/media?parent=164"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/categories?post=164"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/tags?post=164"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}