combining RMI, REST and a DHT technology solution 2

This will test your ability to use each of these technologies and to integrate them. Tasks will be submitted by the user to a REST service; allocated to a “worker” node in a DHT which will execute the task; with results later collected from the DHT by the REST service. The definition of “a task” is given below. A basic solution must demonstrate the ability for the user to upload a task, for that task to be assigned to a DHT node and (asynchronously) executed there, and for the user to later download the results of that task from the REST service. Note that your DHT implementation must use RMI for inter-node communication. Also note that you can easily place RMI “client-side” code into your REST class but you should not attempt to also use it as an RMI “server” (see tips section below). you must generalise your implementation to accept multiple different types of task (at least 3). You will need to design a way of describing what kind of task is being submitted so that the task processing nodes know which kind of processing to use on the associated input file. Additionally, your REST server should provide an intuitive way of showing which tasks have been completed (so their results are ready to be downloaded) and what kind of task each completed task is. Definition of a Task For the purposes of this exercise a computation task is assumed to be a text document which should be analysed to determine: (i) the total number of words; (ii) the most frequently occurring word; and (iii) the average word length. The results should be returned as an XML file with this information.