1 / 24

Implementing Remote Procedure Calls

Implementing Remote Procedure Calls. Andrew Birrell and Bruce Nelson. Presented by Kai Cong. Conventional Procedure Calls . main. proc 1. proc 2. proc 3. proc 4. proc 5. proc 6. proc 7. proc 8. Within a program On a single computer!!!. Extension of the Procedural Model.

hawa
Download Presentation

Implementing Remote Procedure Calls

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementing Remote Procedure Calls Andrew Birrell and Bruce Nelson Presented by Kai Cong

  2. Conventional Procedure Calls main proc1 proc2 proc3 proc4 proc5 proc6 proc7 proc8 Within a program On a single computer!!!

  3. Extension of the Procedural Model computer1 computer2 main proc1 proc2 proc3 proc4 proc5 proc6 proc7 proc8 Across a network between programs On different computers!!!

  4. Remote Procedure Call (RPC) Client Server Blocked Request Blocked Computing Reply Blocked

  5. RPC – How it works client process server process client procedure call server procedure RPC Runtime module RPC Runtime module client stub locate (un)marshal (de)serialize send (receive) server stub (un)marshal (de)serialize receive (send)

  6. Issues • Binding • Passing data • Implementation • Exceptions • RPC systems

  7. Binding • The binding operation is to bind an importer of an interface to an exporter of an interface. • After binding, calls made by the importer invoke procedures implemented by the remote exporter. • static binding vs dynamic binding

  8. Static Binding • static binding(not presented by the paper) • hard coded stub • simple • efficient • not flexible • stub recompilation is necessary if the location of the server changes • use of redundant servers is not possible

  9. Dynamic Binding • dynamic binding • Interface: type and instance • Database • load balancing • flexible • redundant servers is possible

  10. Dynamic Binding client process server process client procedure call server procedure 3 server stub register (un)marshal (de)serialize receive send client stub bind (un)marshal (de)serialize find send receive 7 1 RPC Runtime module RPC Runtime module 7 4 5 6 2 Database

  11. Issues • Binding • Passing data • Implementation • Exceptions • RPC systems

  12. Passing Data • Can't use the stack! • Can't use shared memory! • Generally use message passing

  13. Passing data Build a message that includes: • Who and what's being called • Identity of the caller • Data values in known byte order • Using an intermediate data representation

  14. Issues • Binding • Passing data • Implementation • Exceptions • RPC systems

  15. Implementation

  16. Implementation • Function prototype is (almost) all that's needed to build the client stub • Also need binding information • Function prototype is (almost) all that's needed to build server stub • Also need method to wait for message

  17. Implementation • Stub compiler • Generates stubs for client and server • Language dependent • Compile into machine-independent format • Transport protocol • PUP, XML, SOAP, DCOM, CORBA, …

  18. Implementation • Clients • Threaded • Servers • Event Driven

  19. Issues • Binding • Passing data • Implementation • Exceptions • RPC systems

  20. Exceptions • What can happen in "normal" procedures? • Procedure generates an exception • Procedure infinite loops • Procedure generates wrong results

  21. Exceptions • What can happen in "remote" procedures? • Client stub generates an exception • Transmission failure • knowable failure • unknowable failure • Remote procedure generates an exception • Remote procedure infinite loops • Remote procedure generates wrong results

  22. Issues • Binding • Passing data • Implementation • Exceptions • RPC systems

  23. RPC Systems Sun RPC DCE RPC DCOM CORBA Java RMI XML RPC, SOAP/.NET, AJAX, REST Protocol Buffers (Google) Thrift (Facebook)

  24. Conclusion • Remote Procedure Call should look and feel like local call • Remote Procedure Call should be independent of where it executes • Remote Procedure Call should be "efficient“

More Related