20 Nov You will implement a reliable FTP client-server system. Provide a simple menu to the user, e.g. 1. GET 2. PUT 3. CD 4. QUIT Your code must be robust and handle any incorrect user input.
You will implement a reliable FTP client-server system. Provide a simple menu to the user, e.g. 1. GET 2. PUT 3. CD 4. QUIT Your code must be robust and handle any incorrect user input. Since there can be multiple clients querying the server at the same time with each client being serviced by a different thread on the server, the server must ensure concurrency control on the data file while it is being updated. Thus, only one thread must gain access to the data file during writes (hint: use synchronized keyword for the write method in your code). Be sure to terminate each thread cleanly after each client request has been serviced. Implement the project as described using Java Datagrams (UDP). This will be a connectionless client-server system since UDP is connectionless. However, you will need to provide reliability in your client-side application code since UDP does not guarantee delivery. You may use the CRC32 checksum class available in the java.util.zip package in the JDK for this purpose. Refer to: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/zip/CRC32.html for a description of this API. Sample code is at: https://codingexplained.com/coding/java/generate-crc32-checksum-in-java In each project, be sure to measure the mean response time for the server to service the client request. To graph this, have your client make requests in the order of the following data/file sizes: 1 MB, 25 MB, 50 MB, 100 MB. First do this for the PUT command and then do this for the GET command. Determine the response time in each case, then plot the response time vs. offered load (file size) graph. Next, plot the throughout versus offered load graph using the data from the GET graph/command. Throughput in this case is bytes delivered per second (bytes/second). Plot the bytes/second on the y-axis and offered load on the x-axis. So, at the end of each project, you will have 3 graphs: one graph for the response time for the GET command, one graph for the response time for the PUT command, and the throughput graph for the GET command. Your code must be well documented with adequate comments, suitable use of variable names, and follow good programming practices.