Yves and Eddy, This change looks good. Can I request another small change, thought? For sticky and sticky-unique, can you change the first "but" to "and"? ... used when a data is kept inside the platform and cannot be moved between the servers ... Dan On Mar 25, 2011, at 11:03 AM, Eddy Caron wrote:

Dear Daniel,

After discussions, we have improved the definition of GRPC_STICKY. Definitions are now:

– GRPC STICKY: used when a data is kept inside the platform but cannot be moved between the servers, except if the user explicitly ask for the migration. This is used if the client needs that data in the platform for a second computation on the same server for example. Note that in this case, the data can also be replicated and that potential coherency issues may arise.

– GRPC PERSISTENT: used when a data has to be kept inside the platform. The underlying data middleware is explicitly asked to handle the data: the data can migrate or be replicated between servers depending on scheduling decisions, and potential coherency issues may arise if the user attempt to modify the data on his own.

With you external point of view, do you think it's more clear and enough ?

Thanks you for your feedback.

Best Regards Yves and Eddy

<GRPC_Data.pdf> ---------------------------------------------------------------------------------------------- Eddy Caron. Mcf ENS Lyon ENS Lyon - LIP - Projet GRAAL 46 Allee d'Italie, 69364 Lyon Cedex 07, France E-Mail : Eddy.Caron@ens-lyon.fr [ Tel : 04.37.28.76.46 ][ Web page : http://graal.ens-lyon.fr/~ecaron ] ------------------------------------------------------------------------------------------------

-- Daniel S. Katz University of Chicago (773) 834-7186 (voice) (773) 834-3700 (fax) d.katz@ieee.org or dsk@ci.uchicago.edu http://www.ci.uchicago.edu/~dsk/