UDP Server client pinger

UDP Pinger In this programming assignment, you will write a client ping program in C++. Your client will send a simple ping message to a server, receive a corresponding pong message back from the server, and determine the delay between when the client sent the ping message and received the pong message. This delay is called the Round Trip Time (RTT). The functionality provided by the client and server is similar to the functionality provided by standard ping program available in modern operating systems. However, standard ping programs use the Internet Control Message Protocol (ICMP) (which we will study in Chapter 4). Here we will create a nonstandard (but simple!) UDP-based ping program. Your ping program is to send 10 ping messages to the target server over UDP. For each message, your client is to determine and print the RTT when the corresponding pong message is returned. Because UDP is an unreliable protocol, a packet sent by the client or server may be lost. For this reason, the client cannot wait indefinitely for a reply to a ping message. You should have the client wait up to one second for a reply from the server; if no reply is received, the client should assume that the packet was lost and print a message accordingly. In this assignment, you will be given the complete code for the server (available in myCourses). Your job is to write the client code, which will be very similar to the server code. It is recommended that you first study carefully the server code. You can then write your client code, liberally cutting and pasting lines from the server code. What to hand in? 1. Submit code with in-line documentation 2. Run your code on your local machine as well as on ‘remote’. A design document outlining the design decisions you made and also sample outputs (screenshots), which show that you program works correctly. Please include screenshots that show that your code runs correctly on your machine as well as on remote. If you had to make any changes to run your code on remote, please mention that in your design document. 3. A brief description of cases where you code might fail and possible ways of improving your program.