GridRPC

This paradigm has been proposed by the GridRPC working group [1] of the Open Grid Forum (OGF), and an API has been defined[2] in order for clients to access remote servers as simply as a function call.

It deals with the following topics: Among existing middleware and application programming approaches, one simple, powerful, and flexible approach consists in using servers available in different administrative domains through the classical client-server or Remote Procedure Call (RPC) paradigm.

Clients submit computation requests to a resource broker whose goal is to find a server available on the Grid.

Transparently through the Internet, large optimization problems can be solved using different approaches by simply filling a web page for remote image processing computations, the use of mathematical libraries or studies on heuristics and resolution methods for sparse linear algebra like GridTLSE.

One step to ease the development of such codes conducted to define a GridRPC API, which has been proposed as a draft in November 2002[6] and which is an Open Grid Forum (OGF) standard since September 2007.

Mechanisms involved in the API must provide means to make synchronous and/or asynchronous calls to a service.

This naturally involves some data structures and conducts to a rigorous definition of the functions of the API.

It is explicitly invalidated by the user when not needed anymore; (2) grpc_session_t is the type of variables used to identify a specific non-blocking GridRPC call.

grpc_get_handle() let the client retrieve the function handle corresponding to a session ID (e.g., to a non-blocking call) that has been previously performed.