This preview shows page 1. Sign up to view the full content.
Unformatted text preview: sage: whether to retransmit the request message until either a reply or the server is assumed to have failed;
– Duplicate filtering : when retransmission are used, whether to filter out duplicates at the server;
– Retransmission of replies: whether to keep a history of reply messages to enable lost replies to be retransmitted without reexecuting the server operations. CSC 8320 RPC Slide 11 Call Semantics Maybe call semantics – After a RPC timeout (or a client crashed and restarted), the client is not sure if the RP may or may not have been called. – This is the case when no fault tolerance is built into RPC mechanism. – Clearly, maybe semantics is not desirable. CSC 8320 RPC Slide 12 Call Semantics Atleastonce call semantics
– With this call semantics, the client can assume that the RP is executed at least once (on return from the RP).
– Can be implemented by retransmission of the (call) request message on timeout. – Acceptable only if the server’s operations are idempotent. That i...
View Full Document
- Spring '14