Remaining problems

• An unsolved problem dealing with omniORB and JNI results in a failure when a JNI SeD registers to a DIET Agent not launched via JNI. Because of that, to deploy some LAs between a DIET MA and a DIET SeD, they have to be launched via JNI. Moreover, a DIET MA won't be able to know LAs or SeDs not launched via JNI. The current DIET tree is unable to contain classic LAs or SeDs.

• The current version of the DIET platform works only for problems having two input matrices and one output matrix. The serialization has been written only for these cases. One of the first things to do is to write a generic packing and unpacking, to be able to process all problems supported by DIET.
• The client isn't very simple to write, because nothing is hidden to the user, neither the details of the JXTA communication nor the creation of the problem. As for the client, an API providing all mechanisms needed to communicate with DIET via JXTA pipes should be written. The implementation of a Java Client taking in account the JXTA communication seems to be the solution.