Remote Technique Call Down to earth Issues

2099 days ago, 720 views
PowerPoint PPT Presentation
Pragmatic Issues of RPC. CS-4513, D-Term 2007. 2. Audit. Message-arranged communicationConnectionsEstablishing an association with a serviceReliable correspondence by means of TCPConnection-less correspondence through UDPRemote Procedure CallProcedural interface in the middle of customer and serviceIDL

Presentation Transcript

Slide 1

Remote Procedure Call Practical Issues CS-4513 Distributed Computing Systems (Slides incorporate materials from Operating System Concepts , 7 th ed., by Silbershatz, Galvin, & Gagne, Modern Operating Systems , 2 nd ed., by Tanenbaum, and Distributed Systems: Principles & Paradigms , 2 nd ed. By Tanenbaum and Van Steen) Practical Issues of RPC

Slide 2

Review Message-situated correspondence Connections Establishing an association with an administration Reliable correspondence by means of TCP Connection-less correspondence by means of UDP Remote Procedure Call Procedural interface amongst customer and administration IDL & stub compiler (shrouds correspondence subtle elements) Hiding information representation contrasts Restrictions on passing articles by reference Practical Issues of RPC

Slide 3

Practical RPC Systems DCE (Distributed Computing Environment) Open Software Foundation Basis for Microsoft DCOM Tanenbaum & Van Steen, §4.2.4 Sun's ONC (Open Network Computing) Very like DCE Widely utilized rpcgen Practical Issues of RPC

Slide 4

Practical RPC Systems (proceeded with) Java RMI (Remote Method Invocation) java.rmi standard bundle Java-arranged approach — items and techniques CORBA (Common Object Request Broker Architecture) Standard, multi-dialect, multi-stage middleware Object-situated Heavyweight … Practical Issues of RPC

Slide 5

Implementation Model for DCE Practical Issues of RPC

Slide 6

Differences for ONC program & variant # program & form # rpcgen Practical Issues of RPC

Slide 7

Validating a Remote Service Purpose Avoid authoritative to wrong administration or wrong form DCE Globally remarkable ID Generated in format of IDL record Sun ONC Program numbers enrolled with Sun Version # and strategy # regulated locally Practical Issues of RPC

Slide 8

RPC Binding — Sun ONC Service registers with portmapper on server OS Program # and rendition # Optional static port # Client Must know have name or IP address clnt_create(host, prog, vers, proto) I.e., RPC to portmapper of host asking for to tie to prog, vers utilizing convention proto ( tcp or udp ) (Additional capacities for confirmation, and so forth.) Invokes remote capacities by name Practical Issues of RPC

Slide 9

Sun ONC (proceeded) #include <rpc/rpc.h> Header petition for customer and server rpcgen The stub compiler Compiles interface.x Produces .h documents for customer and administration; likewise stubs See additionally rpcinfo RPC Programming Guide Practical Issues of RPC

Slide 10

Note on XDR (the interface definition dialect for ONC) Much like C Exceptions string sort – maps to singe * bool sort – maps to bool_t Practical Issues of RPC

Slide 11

Sun ONC Online instructional exercise CS-4513 code tests Any different assets you can discover Practical Issues of RPC

Slide 12

Java RMI Based on articles & strategies I.e., a question might be found remotely Accessed through techniques RMI causes strategies to be conjured by RPC Stubs might be nearby or remote Subject to security approach Practical Issues of RPC

Slide 13

Java RMI Binding Remote items must be enlisted with RMI registry May determine a port Security approach ordered with protest Client looks into protest by means of Naming technique Specifies have (& port , if necessary) Remote stubs conveyed with query , subject to security strategy Practical Issues of RPC

Slide 14

Java Remote Object points of interest Interface must amplify java.RMI.Remote Must be open No new techniques presented by java.RMI.Remote Should likewise develop java.rmi.server.UnicastRemoteObject Replaces some Object class techniques for legitimate operation in appropriated environment Must toss java.rmi.RemoteException May affect meaning of existing interfaces Practical Issues of RPC

Slide 15

Java Remote Object points of interest (kept) Compiling article and stubs Object accumulated to bytecodes with javac Stubs incorporated with rmic RMI registry must keep running before remote protest can be propelled rmiregistry summon (a portion of JDK circulation) Multiple registries conceivable on various ports Remote question registers itself java.rmi.Naming interface Practical Issues of RPC

Slide 16

Java Client points of interest Initialize RMI security administrator System.setSecurityManager (… ) If no security director, just neighborhood stubs might be stacked Client must discover and tie to remote protest query () strategy in java.RMI.Naming Location of remote question indicated in URL style E.g., "rmi://" Remote stubs stacked by query Per security approach Practical Issues of RPC

Slide 17

Java RMI CS-4513 illustrations Uses terms "intermediary" and "skeleton" for "customer side stub" and "administration side stub" individually Identifies issues with SYNCHRONIZED remote articles Tanenbaum & Van Steen §10.3, esp. §10.3.4 Any different assets you can discover Practical Issues of RPC

Slide 18

Questions? Handy Issues of RPC

Slide 19

Fundamental Issue With Sun ONC and Java RMI, customer must know name or address of server machine stuck request to tough situation to remote administration IP address or remote name (Sometimes) port number I.e., administrations are bound to server machines Practical Issues of RPC

Slide 20

Problems Location of remote items not generally known Location of remote articles not generally consistent Pointers/References to remote administrations are just helpful to settled servers Distributed & repeated administrations are troublesome, best case scenario Location freedom is unthinkable … Practical Issues of RPC

Slide 21

Needed Location-autonomous question registry Any protest can enlist itself Location-free question naming Name of question does not suggest area Distributed, duplicated registry If any example goes down, others can serve Distributed, imitated remote questions Any occasion may serve much of the time … Practical Issues of RPC

Slide 22

Solutions Some or these things are normally given in the major dispersed protest principles DCOM, CORBA, and so forth. "Worldwide" registry is focal segment Practical Issues of RPC

Slide 23

But … None truly hit the nail on the head for expansive range of dispersed frameworks & applications E.g., CORBA Very heavyweight (excessively bulky) Object can live in one and only area Inefficient for generally got to objects Distributed, imitated protest hard to bolster Practical Issues of RPC

Slide 24

Reading Assignment "Grapevine: An Exercise in Distributed Computing," Communications of the ACM , April 1982 PDF connect Practical Issues of RPC

Slide 25

Break Practical Issues of RPC