Thank you Yves! We've just finished the session. Here is some comments raised in the session. - 4.3.2 grpc_data_mapping _set/get the second argument should be 'void *' instead fo 'grpc_data_t *'. - the name 'grpc_data_init' might be missleading, since it can be applied on the same handle several times. one idea will be - change the name, say, 'grpc_data_populate' another idea will be - have another function named 'grpc_data_update' - the lists in the figures are too small - give us few more examples so that readers can understand which part of the argument is essential and which part is not. All, please take a look and send us comments! cheers, -- HIDEMOTO NAKADA, Ph.D, AIST, Japan On Mon, Sep 15, 2008 at 10:15 AM, Yves Caniou <yves.caniou@ens-lyon.fr> wrote:
Dear All,
To make fast, I put the last version of the document in http://graal.ens-lyon.fr/~ycaniou/GridRPC/
-> http://graal.ens-lyon.fr/~ycaniou/GridRPC/GRPC_Data-0.8.pdf Soon, this will be available on the forge...
The changelog is:
*Added GRPC_STRING, GRPC_FILE types * Put protocols in lower caps * Keyword "LOCAL_MEMORY" is now "memory" * Added section specific to type and mode: - for mapping function (for the memory protocol) - for the container management
There is still work to do at least on error management.
Best Regards.
.Yves.
-- Yves Caniou Associate Professor at Université Lyon 1, Member of the team project INRIA GRAAL, LIP / ENS-Lyon 46 Allée d'Italie 69364 LYON Cedex 07 tel: +33 4 37 28 76 48 http://graal.ens-lyon.fr/~ycaniou/
-- gridrpc-wg mailing list gridrpc-wg@ogf.org http://www.ogf.org/mailman/listinfo/gridrpc-wg