next up previous contents
Next: Examples Up: Building a client program Previous: Structure of a client   Contents

Client API

The client API follows the GridRPC definition [23]: all diet_ functions are ``duplicated'' with grpc_ functions. Both diet_initialize/grpc_initialize and diet_finalize/grpc_finalize belong to the GridRPC API.

A problem is managed through a function_handle, that associates a server to a problem name. For compliance with GridRPC DIET accepts diet_function_handle_init, but the server specified in the call will be ignored; DIET is designed to automatically select the best server. The structure allocation is performed through the function diet_function_handle_default.

The function_handle returned is associated to the problem description, its profile, in the call to diet_call.

The DIET Team - Ven 6 jul 2012 11:19:05 CEST