Abstract This paper proposes a new Remote Procedure Call (RPC) binding model, in which some interaction between the three parties of the system occurs (client, server and binder). The new model uses the server status and the load volume parameters to be exchanged between the parties. The experimental results revealed that the new model is able to decrease the number of retransmitted RPCs due to response time out increasingly when the request rate increase, and decreased the average execution time for a RPC (time needed to send RPC and receive the reply). Moreover, it was also able to increase the load balancing between the servers. Keywords: Remote Procedure Call, Binder, Client, Server. 1. Introduction Distributed systems are constructed of multiple independent computers that appear to its user as a single coherent system. The client-server model is a standard model for these systems, where the client might request a procedure that exists on another server in the network. Using a middleware communication channel clients would be able to send their Request to the servers and receive a reply as shown in figure 1, such communication process is called Remote Procedure Call (RPC) [8].
[1]
Raj Srinivasan,et al.
RPC: Remote Procedure Call Protocol Specification Version 2
,
1995,
RFC.
[2]
Wanlei Zhou,et al.
Managing Replicated Remote Procedure Call Transactions
,
1999,
Comput. J..
[3]
Michael L. Scott,et al.
Integrating remote invocation and distributed shared state
,
2004,
18th International Parallel and Distributed Processing Symposium, 2004. Proceedings..
[4]
Markus Pizka.
Improving Distributed OS Performance by Flexible Incremental Linking
,
2003,
PDPTA.
[5]
Sajjan G. Shiva,et al.
Implementation of reliable and efficient remote procedure calls
,
1993,
Proceedings of Southeastcon '93.
[6]
Xin Chen,et al.
A Procedure Search Mechanism in OGSA-Based GridRPC Systems
,
2003,
GCC.
[7]
Henri Casanova,et al.
Overview of GridRPC: A Remote Procedure Call API for Grid Computing
,
2002,
GRID.