Inter process communication - CMD chat tool and more functionality

Linux programming: C language. must be done before 13/5/2023. Task – IPC Your goal is to implement a chat tool, that will help to set some performance tests. Part A: basic functionality Implement a chat cmd tool that can send messages over the network, to the same tool, listening on the other side, and get the response, so there will be 2 sides communicating, simultaneously Name the tool stnc. The usage s like this: The client side: stnc -c IP PORT The server side: stnc -s PORT the communication will be done using IPv4 TCP protocol By “chat” we mean a tool that can read input from the keyboard, and at the same time listen to the socket of the other side. Part B: performance test Extend the tool, to make it a network performance test utility. You can use your chat channel, for system communication, like transferring states, times, etc. By performance test, we mean the next task. 1) Generate a chunk of data, with 100MB size 2) Generate a checksum (hash) for the data above 3) Transmit the data with the selected communication style, while measuring the time it takes 4) Report the result to stdOut communications styles are: tcp/udp ipv4/ipv6 (4 variants) mmap a file. Named pipe (2 variants) Unix Domain Socket (UDS): stream and datagram (2 variants) usage: The client side: stnc -c IP PORT -p <type> <param> -p will indicate to perform the test <type> will be the communication types: so it can be ipv4,ipv6,mmap,pipe,uds <param> will be a parameter for the type. It can be udp/tcp or dgram/stream or file name: You have only 8 combinations: ipv4 tcp ipv4 udp ipv6 tcp ipv6 udp uds dgram uds stream mmap filename pipe filename The server side: stnc -s port -p (p for performance test) -q (q for quiet) -p flag will let you know that we are going to test the performance. -q flag will enable quiet mode, in which only testing results will be printed. (This is extremely important for the automatic test.) the results will be in milliseconds (ms) and printed like this name_type,time Examples: ipv4_udp,112233 uds_stream,112233 mmap,223355 pipe,554411 Notes: • It’s clear that the performance test tool is NOT a chat tool, so there is no expectation to have a conversation before or after the test. Both the client and the server will finish once the test of the requested type is done • You can use the ./ command then needed. As it’s a port of a command to a shell to exec a code, it's not listed on the usage sections • If there is an error in parameters, like missing params, or giving some malformed text, print the help/usage text (in any form) and exit • It’s highly suggested to use the Beej IPC Guide, available at [login to view URL] • the task is meant to be done with poll/select API, and without threads