The application behaves like a client and a server at the same time.
1. The server role.
It waits for a message from client. When a message is received it processes it.
The 1st message would be a query, asking if a certain file exists on the system
The response should be YES/NO
The 2nd message would request the file
The server should start sending the file in parts. The size of each part would depend on
the size of the file. You need to decide what should be the size of each part.
Your design should consider lost parts during transmission, out of order parts arriving,
and finally some metho to indicate that the file trnsfer is complete.
2. Client role
There should be a command interface where you are trying to get a file using file name.
(for added functionality, consider partial file name, or just file types - .jpg, mpeg etc.)
The client should send a message to N servers.
The client recevies replies from N-X servers. Some o the replies will be "YES" others will be "NO"
Select one of the servers that replied "YES". Request the file from the server.
The file may arrive in parts. reassemle the file.
35 freelancers are bidding on average $150 for this job
hi... i can do this. please let me know to start immediately. provide more information about the job. please initiate communication to discuss further. thanks
Hello sir, i did client/server applications many times either in C++ or java. i know how to do it. Let me know your decision about the language to be used. (i preferred java). Am Ready to start... Thanks