RPC, RMI and CORBA

More documents

Recommendations

Info

Specification of the OperationsIn pseudo-Java:Message DoOperation(PortId server, Message msg)• the returned message is the result of SendReply• blockingMessage GetRequest(PortId server)• acquires a request message• blockingvoid SendReply(PortId client, Message msg)• sends a reply messageinterface Message {}MessageType type;int requestId;int methodId;Object[] arguments;// request or reply// matches replies to requests// method to execute// flattened list
Delivery Failures• In the general case• messages are occasionally dropped by senders,receivers, <strong>and</strong> the network• networks may become partitioned• processes may fail• not generally distinguishable from network failure• typically assume failure after N requests; choosing a good N is ahard problem• received data is corrupted• To account for this, DoOperation should have atimeout associated with it; other steps arenecessary
Page 1: Object-based DistributedSystemsEEE4
Page 4 and 5: Design Exercise - a remote procedur
Page 6: Programming Model• integrated int
Page 10 and 11: Define a Remote Interface• the in
Page 12 and 13: Make Available to Users• “boots
Page 14 and 15: Client Side: Obtain a Remote Refere
Page 16 and 17: Java RMI Development ProcessDevelop
Page 18 and 19: Structure of an RMI Application•
Page 20 and 21: Remote Object Implementation
Page 22 and 23: RMI Mechanism• Work through colla
Page 24 and 25: package server;import java.rmi.regi
Page 26 and 27: This file was generated by the RMI
Page 28 and 29: Review• RMI Semantics
Page 32 and 33: Possible Exchange Protocols• Look
Page 34 and 35: Duplicate Requests• Since client
Page 36 and 37: History• When a server cannot saf
Page 38: Examples:• Specify:• the semant

RPC, RMI and CORBA

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?