]uname - - gnu/linux ]python fork-server py server connected by ( ' at sat apr : : server connected by ( ' at sat apr : : server connected by ( ' at sat apr : : [client window :\pp \internet\socketspython echo-client py learning-python com client receivedb"echo=> 'hello network worldat sat apr : : [client window :\pp \internet\socketspython echo-client py learning-python com bruce client receivedb"echo=> 'bruceat sat apr : : [client window :\socketspython echo-client py learning-python com the meaning of life client receivedb"echo=> 'theat sat apr : : client receivedb"echo=> 'meaningat sat apr : : client receivedb"echo=> 'ofat sat apr : : client receivedb"echo=> 'lifeat sat apr : : againall times here are on the server machine this may be little confusing because four windows are involved in plain englishthe test proceeds as follows the server starts running remotely all three clients are started and connect to the server few seconds apart on the serverthe client requests trigger three forked child processeswhich all immediately go to sleep for five seconds (to simulate being busy doing something useful each client waits until the server replieswhich happens five seconds after their initial requests in other wordsclients are serviced at the same time by forked processeswhile the main parent process continues listening for new client requests if clients were not handled in parallel like thisno client could connect until the currently connected client' fivesecond delay expired in more realistic applicationthat delay could be fatal if many clients were trying to connect at once--the server would be stuck in the action we're simulating with time sleepand not get back to the main loop to accept new client requests with process forks per requestclients can be serviced in parallel notice that we're using the same client script here (echo-client pyfrom example - )just different serverclients simply send and receive data to machine and port and don' care how their requests are handled on the server the result displayed shows byte string within byte stringbecause the client sends one to the server and the server sends one backbecause the server uses string formatting and manual handling multiple clients