The biggest difference between this server and the echo server is the call to lsock.setblocking(False) to configure the socket in non-blocking mode. Calls made to this socket will no longer block . When it's used with sel.select() , as you'll see below, you can wait for events on one or more sockets and then read and write data when it's ready. State diagram for server and client model of Socket Stages for server 1. Socket creation: int sockfd = socket (domain, type, protocol) sockfd: socket descriptor, an integer (like a file-handle) domain: integer, specifies communication domain. We use AF_ LOCAL as defined in the POSIX standard for communication between processes on the same host. ¢ They take a request from one computer (ac4ng as the server), and make it on their behalf (as the client). ¢ Ul4mately, the control flow of your program will look like a server, but will have to act as a client to complete the request ¢ Start small § Grab yourself a copy of the echo server (pg. 946) and client (pg. One option to run these commands is to invoke cmd.exe, for example cmd /C echo hello. Alternatively Julia can be run inside a Posix environment such as Cygwin. Here's a simple example of running an external program: julia> mycommand = `echo hello` `echo hello` julia> typeof (mycommand) Cmd julia> run (mycommand); hello The Simple Client corresponding to the previous server (and to step 2 and step 3 servers as well): import java.net.*; import java.io.*; public class ChatClient { private Socket socket = null; private DataInputStream console = null; private DataOutputStream streamOut = null; public ChatClient(String serverName, int serverPort) { System Note that UnixDatagramServer derives from UDPServer, not from UnixStreamServer — the only difference between an IP and a Unix stream server is the address family, which is simply repeated in both Unix server classes.. class socketserver.ForkingMixIn¶ class socketserver.ThreadingMixIn¶. Forking and threading versions of each type of server can be created using these mix-in classes. This is the third and final article in a series about interprocess communication (IPC) in Linux. The first article focused on IPC through shared storage (files and memory segments), and the second article does the same for basic channels: pipes (named and unnamed) and message queues. This article moves from IPC at the high end (sockets) to IPC at the low end (signals). We can start implementing sockets in our progam with three simple steps: Import Socket Library To use a socket object in your program, start off by importing the socket library. No need to install it with a package manager, it comes out of the box with Python. import socket Build Socket Objects Now we can create socket objects in our code. First run server.c file and create an output file for that in Unix or Linux. Type gcc server.c -o server command in terminal. Now run the server using ./server. After running the server just minimize the terminal. Open new terminal. Do remaining work there. To know the server is running or not we can check using netstat command. Threads operate faster than processes due to following reasons: 1) Thread creation is much faster. 2) Context switching between threads is much faster. 3) Threads can be terminated easily 4) Communication between threads is faster. See personal.kent.edu/~rmuhamma/