CSE4001 Study Guide - Distributed Object Communication, Java Remote Method Invocation, Inetd

21 views6 pages

Document Summary

Two design issues that arise in extension of local method invocation for rmi: the choice of invocation semantics. Make remote invocation as much like local invocation as possible. Choices of invocation semantics: maybe: the method executed once or not at all (no retry nor retransmit, at-least-once: the method executed at least once, at-most-once: the method executed exactly once. Transparent remote invocation: like a local call: marshalling/unmarshalling, locating remote objects, accessing/syntax. Syntax might need to be different to handle different local vs remote errors/exceptions (e. g. argus: consistency on the remote machine: Argus: incomplete transactions, abort, restore states [as if the call was never made] Two cooperating communication modules carry out the request-reply protocols: message type, request id, remote object reference. Transmit request and reply messages between client and server. Implement specific invocation semantics: the communication module in the server. Selects the dispatcher for the class of the object to be invoked, Passes on local reference from remote reference module,

Get access

Grade+
$40 USD/m
Billed monthly
Grade+
Homework Help
Study Guides
Textbook Solutions
Class Notes
Textbook Notes
Booster Class
10 Verified Answers

Related Documents

Related Questions