N/APosted on - 06/06/2012
I would like to know about the RPC Mechanism and the outcome that can be caused if at-most- once call semantics or exactly-once semantics is not implemented.
Is there any other system that does not assure any of this?
I would like to know about the RPC Mechanism?
RPC is an interprocess communication mechanism that enables data exchange and invocation of functionality residing in a different process, RPC is designed to facilitate communication between client and server processes. The functions contained within RPC are accessible by any program that must communicate using a client/server methodology.
The RPC components make it easy for clients call a procedure located in a remote server program. The client and server each have their own address spaces, that is, each has its own memory resource allocated to data used by the procedure.
When the server receives the RPC, either locally or from a remote client, the server RPC runtime library functions accept the request and call the server stub procedure. The remote procedure then runs, possibly generating output parameters and a return value.
RPC has 3 Semantics that are Exactly once, At most once and At least once semantics.