Distributed file service with consistancy

Client Upon startup, the client will perform the following actions: Startup: 1. Prompt the user to input a username. 2. Connect to the server over a socket and register the username. a. When the client is connected, the user should be notified of the active connection. b. If the provided username is already in use, the client should disconnect and prompt the user to input another username. 3. Proceed to manage the consistency of the shared file until killed by the user. Updating Files: 1. The client will actively monitor the designated text file. 2. When an update to the file is noted, the client will notify the user of the update. 3. The client will then Push the updated file to the server. The user should be notified when the upload is complete. 4. Return to step 1. Retrieving Updates: 1. The client will listen for an Invalidation Notice from the server. 2. Upon receipt of the notice, the client will Pull the update and apply the update to its copy of the shared .txt file. 3. The client will inform the user that an update has been completed. 4. Return to step 1. Server The server should support three concurrently connected clients and display a list of which clients are connected in real-time. The server will execute the following sequence of steps: 1. Startup and listen for incoming connections. 2. Print that a client has connected, and: a. If the client has an available username, fork a thread to handle that client. Or, b. If the username is taken, reject the connection from that client. 3. When a client pushes an update to the server, the server should: a. Accept the data from the client; b. Print that an update has been received and from which client; c. Issue Invalidation Notices to the remaining clients; and, d. Allow the remaining clients to Pull the update. 4. Begin at step 2 until the process is killed by the user.