The client should read input files and send them to the server in the form of a settings struct (using sockets?).
The server:
adds received data to a queue
processes all items in queue
waits for work while queue is empty
Q: Should the server write the results to a file or send them back to the client?
A: Probably best to send back to client
Client may optionally handle a pool of servers and keep 2nd queue of tasks:
make sure a min/max number of tasks are in each server's queue
keep remaining tasks in client queue for load balancing
Actually, instead of putting all this functionality into the client, keep the client simple (only does dispatching and receiving of results) and write a 3rd program for load balancing called poolManager
The client should read input files and send them to the server in the form of a settings struct (using sockets?).
The server:
Q: Should the server write the results to a file or send them back to the client? A: Probably best to send back to client
Client may optionally handle a pool of servers and keep 2nd queue of tasks:
Actually, instead of putting all this functionality into the client, keep the client simple (only does dispatching and receiving of results) and write a 3rd program for load balancing called
poolManager