The client

Only one component, the client, is fully written in java. Since it communicates only with JXTA components, it doesn't need the DIET client library. JXTA pipes do not allow all types of data to be sent through. The description of the problem and the problem itself have to be packed to be sent through JXTA pipes. These messages are unpacked inside the MA and SeD.

The behaviour of the JXTA client is:

• launch a new JXTA peer,
• get MA advertisements (JXTA messages travelling through the network identifying a JXTA object) by sending a JXTA discovery query,
• extract the reference of the input pipe of the first MA advertisement discovered,
• create an output pipe to bind the input pipe extracted,
• create and send the description of the problem via the pipe created and wait for the response of the MA bound, including references of SeDs able to solve the problem,
• Try to create an output pipe to bind the input pipe of one of the SeDs found,
• Send the packed problem including data needed for the computation to the SeD bound and wait for its response,
• Extract results of the response received.