After having solved the subproblem, the Slave establishes a new connection with the Master, identifies itself, sends the results and closes the connection. The Slave can also establish connections to the Master before termination, to send partial results, e.g., when local memory is scarce. After the solution has been sent, the Slave connects again to the Master, asking for another subproblem to solve. This process continues until Slave is stopped or no more subproblems are available from the Master. Upon receipt of results from any Slave, the Master turns the subproblem status to solved and behaves according to the Problem type.
Several action are possible.
Basically the Master stores the subproblem result on disk, for future computations. The result corresponding to the solution of a subproblem can also let the Master know that the solution of the remaining subproblems is not necessary, and that it can proceed to compute the solution of the problem locally. This feature is useful in a number of search problems, e.g., when the goal is to find a certificate that proves that a certain property is true. The Master is a Java application without graphical interface, suitable to run in background. Graphical interface to the Master activities is provided by a set of applets, globally called the Manager, which allow one to remotely control the Master.