Till now we have seen examples wherein the socket connection is between two distinct processes. “socketpair API” socket connection allows a user to create a socket link between a Parent process and it’s child process. Each process (ie. the parent and its child) gets two handles. The parent socket handle and the child socket handle. […]

The code for the AF_UNIX Abstract Namespace datagram socket code example can be found at this link. The APIs and the connection steps are the same for the code as a AF_UNIX UDP socket connection code. The difference is that the socket path is an abstract path.  code snippets from the server code to create […]

The APIs and the steps in establishing data transfer are Similar to a AF_UNIX Datagram socket connection. For the interested reader, the AF_UNIX datagram socket details can be read at the below link locations. AF_UNIX Datagram code example   AF_UNIX Datagram code analysis The difference being that the path for the client and the server are […]

The code for an Abstract Namespace Unix domain (AF_UNIX) socket is provided at the link here. As can be seen in the server and client code, the steps to connect to the stream socket all remain the same on the server and the client side relative to any other stream socket connection. The difference in […]

To get a basic understanding of an abstract Namespace socket connection, refer the article provided here. To create a socket connection path which does not have an entry in the filesystem, the below method is used const char *path= “#unix_socket.sock”; The ‘#‘ in the above name will be replaced with ‘\0‘ (Null byte) when it […]

When we create Unix Domain (AF_UNIX) sockets, we create a socket path in the file system, but what if we do not create a specific file-system path for the socket connection. The abstract namespace socket allows the creation of a socket connection which does not require a path to be created. Abstract namespace sockets disappear […]