[GRIDRPC-WG] Proposal for a Data Management API within the GridRPC

[Yves Caniou]

Dear Yusuke and all,

Sorry to be that late anwering your mail.

Le Tuesday 11 September 2007 11:41:10 Yusuke Tanimura, vous avez écrit :
> Dear Eddy and all,
>
> > 	Yes it's a latex version. We can convert in .doc if needed. With
> > Yves Caniou we have corrected some part of the first version to take
> > into account internal remarks from the GRAAL Team.
> >
> > New version available here (version 0.2):
> >
> > http://graal.ens-lyon.fr/~ecaron/GridRPC/GRPC_Data.pdf
> >
> > Source files are available here :
> >
> > http://graal.ens-lyon.fr/~ecaron/GridRPC/GRPC_Data_OGF21.tar.gz
>
> The spec introduces several new error codes.  If we add
> GRPC_INVALID_TYPE and GRPC_INVALID_MODE to the spec, both could be
> returned in grpc_call() and grpc_call_async(), too, when the
> argument data does not match to what the server program expects.

We had a lot of discussions about returning error codes, and which ones to 
return depending on the case, within a grpc_call().
You are right saying that some kind of errors concerning Data Management can 
extend the GridRPC API and GridRPC interoperability document. For example, 
data transfer errors occuring on the server side could also be returned to 
the client for debugging purposes. For the moment, it can be interesting to 
add a GRPC_DATA_ERROR, without going deeper in the definition.
We suggest to keep the GridRPC Data Management apart from the definition of 
error codes for the moment, which we can discuss later on because of the many 
cases to consider. Of course, all ideas, remarks and commentaries are always 
welcome.

> I feel because data transfer becomes more complicated, a function
> to verify data types and etc. between senders and receivers would
> be helpful for users.

What can be done is to integrate into the GridRPC API a function to load all 
the services on a given server, with their parameter types? 
Of course, some kind of type checking can also be optionally performed when 
issuing the grpc_call(). And corresponding errors can be returned. But as 
said previously, maybe we should split error definitions from GridRPC Data 
Management API for the moment.

Best Regards.

.Yves.