C SOCKET Client/Server

Develop a client-server application based on the C socket API and TCP connections, according to the following specifications: 1. The server receives exactly one argument on the command line: the TCP port number to which it listens. 2. The server must be able to serve concurrently several clients (at least 5, but no more than 20). 3. At startup, the server reads a binary file named [login to view URL] in its local directory and stores its contents in memory. Let us denote k0, k1, ..., kN the bytes of this file. If the file is not found, or if it is too large to be stored in memory, the server must exit immediately with an error message. 4. When connected to a client, the server receives a stream of bytes C=c0, c1, ... from the client and sends back to the client another stream of bytes R=r0, r1, ..., computed from C using the formula attached in PDF (number 5) 5. The connection must be closed gracefully in the following way: a. When the client terminates sending the input stream C, the client closes the client-to-server side of the connection. b. When the server detects that the client has closed the client-to-server side of the connection, the server finishes sending the remaining bytes and then closes the other side of the connection. 6. Client and server must be able to work with input streams of any length. 7. The client receives exactly three command line arguments, exactly in this order: the server name or IP address in dotted decimal notation, the server port number (as decimal number), and the name of a local file. The client must send the contents of this file to the server and store the response received from the server in another file, with a name computed as the concatenation of the original file name and the suffix “_rec”. For example, if the file name is “[login to view URL]”, the file with the server response must be “test.dat_rec”. 8. The client must try to keep the server as busy as possible, by applying this policy: the client must keep sending bytes whenever possible and must receive bytes with lower priority (i.e. only when sending more bytes is impossible). 9. Client and server must be developed for the Linux OS. 10. Design decisions about the implementation of the application are free but must be reasonable ** All payment will be given after completion of project and test