分布式系統(tǒng)中的通信課件

分布式系統(tǒng)中的通信進程間通信是一切分布式系統(tǒng)的核心。分布式系統(tǒng)中的通信都是基于底層網(wǎng)絡提供的低層消息傳遞機制的。通過消息傳遞來描述通信過程比使用基于共享存儲器的原語來描述要更困難。分布式系統(tǒng)中的通信進程間通信是一切分布式系統(tǒng)的核心。14種廣泛使用的通信模型遠程過程調用（remoteprocedurecall,RPC）遠程方法調用（remotemethodinvocation,RMI）面向消息的中間件（message-orientedmiddleware,MOM）面向流的通信（stream-orientedcommunication）4種廣泛使用的通信模型2CommunicationProtocols

由于沒有共享存儲器，分布式系統(tǒng)中的所有通信都是基于（低層）消息交換的。Protocolsareagreements/rulesoncommunicationProtocolscouldbeconnection-orientedorconnectionlessApplicationPresentationSessionTransportNetworkDatalinkPhysicalApplicationprotocolPresentationprotocolSessionprotocolTransportprotocolNetworkprotocolDatalinkprotocolPhysicalprotocolNetwork7654321CommunicationProtocols由于沒3LayeredProtocolsAtypicalmessageasitappearsonthenetwork.2-2LayeredProtocolsAtypicalmes4DataLinkLayerDiscussionbetweenareceiverandasenderinthedatalinklayer.2-3DataLinkLayerDiscussionbetw5Client-ServerInteractionusingTCPNormaloperationofTCP(常規(guī)TCP的許多開銷都耗費在連接的管理上).TransactionalTCP(更經濟的方式).2-4服務器執(zhí)行請求的操作告訴服務器關閉該連接客戶啟動連接建立過程1,2,3要求客戶釋放連接將發(fā)送請求當作連接的建立標志(一個消息包含三條信息)把送回結果當作連接的關閉標志確認連接的終止確認已收到客戶的請求Client-ServerInteractionusin6MiddlewareProtocolsMiddleware:-Anapplicationthatlogicallylivesintheapplicationlayer-Containsmanygeneral-purposeprotocolsthatwarrant（代表）

theirownlayers-(會話層和表示層由一個單一的中間件層代替)ApplicationMiddlewareTransportNetworkDatalinkPhysicalApplicationprotocolMiddlewareprotocolTransportprotocolNetworkprotocolDatalinkprotocolPhysicalprotocolNetwork654321MiddlewareProtocolsMiddleware7Client-ServerCommunicationModelStructure:groupofserversofferingservicetoclients-Servers:offerservicestotheuserscalled“clients”-Clients:applicationsrequiringservicesfromservers-Example:WebServer/clients,Fileserver…Whyuseclient-servermodel-simplicity-low(er)overheadsclientkernelfileserverkernelprocessserverkernelterminalserverkernelClient-ServerCommunicationMo8Client-ServerCommunicationModelBasedonarequest/responseparadigm-Clientssendarequestaskingforservice(e.g.,afileblock)-Serverprocessesandreplieswithresult(orerror)Techniques:-Socket,RemoteProcedureCalls(RPC),RemoteMethodInvocation(RMI)

clientkernelfileserverkernelprocessserverkernelterminalserverkernelClient-ServerCommunicationMo9RemoteProcedureCall(RPC)Client-ServerprovidesamechanismforservicesindistributedsystemsBUT-requiresexplicitcommunication(send-receive)Q:Howdowemake“distributedcomputinglookliketraditional(centralized)computing”?Canweuseprocedurecalls?AcallsB->Asuspended,Bexecutes->Breturns,Aexecutes

?InformationfromA(caller)toB(callee)transferredusingparameters

?SomewhateasiersincebothcallerandcalleeexecuteinthesameaddressspaceRemoteProcedureCall(RPC)Cli10ConventionalProcedureCallParameterpassinginalocalprocedurecall:thestackbeforethecalltoread(fd,buf,nbytes)Thestackwhilethecalledprocedureisactive(執(zhí)行時)調用方(主程序)把參數(shù)、返回地址反序壓入堆棧ConventionalProcedureCallPar11RPCInDistributedsystems:thecalleemaybeonadifferentsystem

-RemoteProcedurecall(RPC,允許程序調用位于其它機器上的進程)-NOEXPLICITMESSAGEPASSING（對編程人員）

從而達到隱藏通信（send和receive），實現(xiàn)分布式系統(tǒng)中的訪問透明性Goal:MakeRPClook(asmuchaspossible)likelocalprocedurecall

-allowremoteservicestobecalledasprocedures-callershouldnotbeawareofthefactthatthecalleeis(executing)onadifferentmachine(orviceversa)Althoughnomessagepassing(atuserlevel),parametersmuststillbepassed&resultsmuststillbereturned!RPCInDistributedsystems:the12ClientandServerStubsPrincipleofRPCbetweenaclientandserverprogram.

客戶通過執(zhí)行普通的（本地）過程調用來訪問遠程服務，它并不需要直接調用Send和Receive，消息傳遞的所有細節(jié)都隱藏在雙方的庫過程（Stub,Skeleton）中。ClientandServerStubs13StepsofaremoteprocedurecallClientprocedurecallsclientstubinnormalwayClientstubbuildsmessage,callslocalOSClient’sOSsendsmessagetoremoteOSRemoteOSgivesmessagetoserverstubServerstubunpacksparameters,callsserverServerdoeswork,returnsresulttothestubServerstubpacksitinmessage,callslocalOSServer’sOSsendsmessagetoclient’sOSClient’sOSgivesmessagetoclientstubStubunpacksresult,returnstoclientStepsofaremoteprocedureca14PassingValueParameters(1)StepsinvolvedindoingremotecomputationthroughRPC2-8PassingValueParameters(1)2-15PassingValueParameters(2)Problem:differentmachineshavedifferentdataformats-Intel:littleendian,SPARC:bigendianSolution:useastandardrepresentation-Example:externaldatarepresentation(XDR)PassingValueParameters(2)Pr16Marshalling:ReferenceParametersProblem:howdowepasspointers?

（指針只在它被使用的進程的地址空間里面是有意義的）-Ifitpointstoawell-defineddatastructure,passacopytotheserverandtheserverstubpasses（使用）

apointertothelocalcopy

(來調用服務器程序）Whataboutdatastructurescontainingpointers?-Prohibit-Copy/restore,

machineindependentrepresentationCallbyCopy/restore:

首先由調用者將變量拷貝到Stack，調用完成之后，將堆棧中的變量復制回去覆蓋調用方該變量原先的值。參數(shù)從客戶發(fā)送到服務器，在那里修改，然后發(fā)送回客戶，覆蓋原來的值。

Marshalling（編組，即把參數(shù)打包進消息中發(fā)送到服務器）:transformparameters/resultsintoabytestreamMarshalling:ReferenceParamet17BindingProblem:howdoesaclientlocateaserver?

（Client要發(fā)送消息到服務器，它需要知道服務器的地址）-UseBindingsServer-Exportserverinterfaceduringinitialization-Sendname,version#,uniqueidentifier,handle(address)tobinderClient(第一次調用遠程過程，還沒有綁定到一個Server）-FirstRPC:sendmsgtobindertoimportserverinterface-Binder:checktoseeifsomeserverhasexportedtheinterface

?ReturnhandleanduniqueidentifiertoclientBinder充當一個注冊服務器的角色。BindingProblem:howdoesacli18Binding:CommentsMethodflexible-canhandlemultipleserverswithsameinterface-bindercanpollaservertoseeifitisupandmayderegisteritifitisdownforfaulttolerance-canenforceauthentication(notgivinginterfacetousernotonlist)ExportingandimportingincursoverheadsBindercanbeabottleneck-UsemultiplebindersBindercandoloadbalancing

隨機地擴展（散播）Clients到這些Servers來平衡負載。Binding:CommentsMethodflexib19AsynchronousRPC(1)TheinterconnectionbetweenclientandserverinatraditionalRPCTheinteractionusingasynchronousRPC2-12AsynchronousRPC(1)Theinterc20AsynchronousRPC(2)AclientandserverinteractingthroughtwoasynchronousRPCs2-13AsynchronousRPC(2)2-1321WritingaClientandaServerThestepsinwritingaclientandaserverinDCERPC.2-14WritingaClientandaServerT22BindingaClienttoaServerClient-to-serverbindinginDCE.2-15BindingaClienttoaServer2-23RemoteMethodInvocation(RMI)RPCsappliedto(distributed)objects,i.e.,instancesofaclass-Class:object-orientedabstraction;modulewithdataandoperations-Separationbetweeninterfaceandimplementation-Interfaceresidesononemachine,implementationonanotherRMIssupportsystem-wideobjectreferences-ParameterscanbeobjectreferencesRemoteMethodInvocation(RMI)24DistributedObjectsWhenaclientbindstoadistributedobject,loadtheinterface(“proxy”)intoclientaddressspace-ProxyanalogoustostubsServerstubisreferredtoasaskeletonClientOSClientinvokesamethodClientServerOSSkeletonServerStateMethodInterfaceProxySkeletoninvokessamemethodatobjectSameinterfaceasobjectClientmachineServermachineObjectNetworkMarshalledinvocationispassedacrossnetworkDistributedObjectsClientOSCl25ProxiesandSkeletonsProxy:clientstub-MaintainsserverID,endpoint,objectID-Setsupandtearsdownconnectionwiththeserver-Doesserializationoflocalobjectparameters-Inpractice,canbedownloaded/constructedontheflySkeleton:serverstub-DoesdeserializationandpassesparameterstoserverandsendsresulttoproxyProxiesandSkeletonsProxy:cl26BindingaClienttoanObjectAnexamplewithimplicitbindingusingonlyglobalreferencesAnexamplewithexplicitbindingusingglobalandlocalreferencesDistr_object*obj_ref; //Declareasystemwideobjectreference

obj_ref=…; //Initializethereferencetoadistributedobject

obj_ref->do_something(); //Implicitlybindandinvokeamethod (a)Distr_objectobjPref; //Declareasystemwideobjectreference

Local_object*obj_ptr; //Declareapointertolocalobjects

obj_ref=…; //Initializethereferencetoadistributedobject

obj_ptr=bind(obj_ref); //Explicitlybindandobtainapointertothelocalproxy

obj_ptr->do_something(); //Invokeamethodonthelocalproxy (b)BindingaClienttoanObjectA27ParameterPassingThesituationwhenpassinganobjectbyreferenceorbyvalue.2-18ParameterPassingThesituation28TheDCEDistributed-ObjectModelDistributeddynamicobjectsinDCE.Distributednamedobjects2-19TheDCEDistributed-ObjectMod29面向消息的通信遠程過程調用和遠程對象調用都有助于隱藏分布式系統(tǒng)中的通信，也就是說增強了訪問透明性。不幸的是，這兩種機制并不總是適用的。特別是當無法保證發(fā)出請求時接收端一定正在執(zhí)行的情況下，就必須有其他的通信服務。同時，RPC和RMI的同步特性也會造成客戶在發(fā)出的請求得到處理之前被阻塞，因而有時也需要采取其他辦法。這里所說的“其他方法”就是消息傳遞機制。面向消息的通信遠程過程調用和遠程對象調用都有助于隱藏分布式系30Message-orientedcommunication-Persistenceandsynchronicity-Message-orientedtransientcommunication

?Berkeleysocket

?MPI-Message-orientedpersistentcommunicationmessage?MessagequeuingsystemsMessage-orientedcommunication31持久通信與暫時通信持久(persistent)通信需要傳輸?shù)南⒃谔峤恢笥赏ㄐ畔到y(tǒng)來存儲，直到將其交付給接收者為止。即在將消息成功交付給下一個通信服務器之前，消息一直存儲在通信服務器中。其典型例子是電子郵件系統(tǒng)。暫時(transient)通信通信系統(tǒng)只在發(fā)送和接收消息的應用程序的運行期間存儲消息。更準確地說，如果通信服務器無法將消息遞送到下一個服務器或者接收者，消息將會被簡單地丟棄。持久通信與暫時通信持久(persistent)通信32異步通信與同步通信異步通信發(fā)送者把要傳輸?shù)南⑻峤恢罅⒓蠢^續(xù)執(zhí)行其其他程序，這意味著該消息存儲在位于發(fā)送端主機的本地緩沖區(qū)中，或者存儲在送達的第一個通信服務器上的緩沖區(qū)中。同步通信發(fā)送者在提交消息之后會被阻塞，直到消息已經到達并存儲在接收主機的本地緩沖區(qū)中以后，也就是消息確實已經傳送到接收者之后,才會繼續(xù)執(zhí)行其它程序。異步通信與同步通信異步通信33PersistenceandSynchronicity:CommentsTransientsynchronouscomm:response-based=>weakerforms,suchasdelivery-basedandreply-basedTransientasynchronouscomm:message-passingsystemsPersistentcomm:developingofmiddlewareforlarge-scaleinterconnectednetworks;failuremaskingandrecoveryPersistenceandSynchronicity:34Message-orientedTransientComm.Manydistributedsystemsbuiltontopofsimplemessage-orientedmodel-Example:Berkeleysockets-AsocketisanabstractrepresentationofacommunicationendpointPrimitiveMeaningSocketCreateanewcommunicationendpointBindAttachalocaladdresstoasocketListenAnnouncewillingnesstoacceptconnectionsAcceptBlockcalleruntilaconnectionrequestarrivesConnectActivelyattempttoestablishaconnectionSendSendsomedataovertheconnectionReceiveReceivesomedataovertheconnectionCloseReleasetheconnectionSocketprimitivesforTCP/IP.Message-orientedTransientCom35BerkeleySocketsConnection-orientedcommunicationpatternusingsockets.BerkeleySocketsConnection-or36TheMessage-Passing

Interface(MPI)Someofthemostintuitivemessage-passingprimitivesofMPI.PrimitiveMeaningMPI_bsendAppendoutgoingmessagetoalocalsendbufferMPI_sendSendamessageandwaituntilcopiedtolocalorremotebufferMPI_ssendSendamessageandwaituntilreceiptstartsMPI_sendrecvSendamessageandwaitforreplyMPI_isendPassreferencetooutgoingmessage,andcontinueMPI_issendPassreferencetooutgoingmessage,andwaituntilreceiptstartsMPI_recvReceiveamessage;blockiftherearenoneMPI_irecvCheckifthereisanincomingmessage,butdonotblockTheMessage-Passing

Interface37Message-orientedPersistentComm.MessagequeuingsystemsorMessage-OrientedMiddleware(MOM)-Supportasynchronouspersistentcommunication-Intermediatestorageformessagewhilesender/receiverareinactive-Exampleapplication:email-支持那些時間要求較為寬松的消息傳輸，比如那些要求幾分鐘完成的傳輸，而適用于那些必須在幾秒內甚至幾微秒內完成的傳輸。(不同于Socket及MPI)Message-orientedPersistentCo38Message-QueuingModel(1)Communicatebyinsertingmessagesinqueues消息由一系列通信服務器依次進行轉發(fā)，最終送達目的地。即使在消息發(fā)送過程中接受者的機器未處于運行狀態(tài)，消息也能送到。原則上，每一個應用程序都擁有歸其私有的消息隊列，其他應用程序可以發(fā)送消息到該隊列中。隊列只能由相應的（也就是擁有該隊列的應用程序）讀取，但是也可能有多個應用程序共享單個隊列。Senderisonlyguaranteedthatmessagewillbeeventuallyinsertedinrecipient'squeue-NoguaranteesonwhenarrivingorifthemessagewillbereadMessage-QueuingModel(1)Commu39Message-QueuingModel(2)Fourcombinationsforloosely-coupledcommunicationsusingqueues.2-26Looselycoupledcommunication

消息進入接收者的消息隊列時，接收者不必處于運行狀態(tài)；即使發(fā)送者沒有運行，接收者也可以讀出發(fā)送給它的消息。發(fā)送者和接收者可以彼此完全獨立地運行。Message-QueuingModel(2)Four40Message-QueuingModel(3)Basicinterfacetoaqueueinamessage-queuingsystem.PrimitiveMeaningPutAppendamessagetoaspecifiedqueueGetBlockuntilthespecifiedqueueisnonempty,andremovethefirstmessagePollCheckaspecifiedqueueformessages,andremovethefirst.Neverblock.NotifyInstallahandlertobecalledwhenamessageisputintothespecifiedqueue.Message-QueuingModel(3)Basic41Example:CommunicationSystem主機通過網(wǎng)絡相連的通信系統(tǒng)的一般組織結構Example:CommunicationSystem主42消息隊列系統(tǒng)消息由（發(fā)送者的）源隊列向（接收者的）目的隊列傳輸。全部隊列的集合是分布在多臺機器上的，因此，對于要傳輸消息的消息隊列系統(tǒng)來說，他應該維護一個由隊列到其所在網(wǎng)絡位置之間的映射關系，即維護一個存儲網(wǎng)絡位置（IP地址）所對應的隊列名的數(shù)據(jù)庫。消息隊列系統(tǒng)消息由（發(fā)送者的）源隊列向（接收者的）目的隊列傳43GeneralArchitectureofaMessage-QueuingSystem(1)Therelationshipbetweenqueue-leveladdressingandnetwork-leveladdressing.GeneralArchitectureofaMess44隊列由隊列管理器來管理。一般來說，隊列管理器與發(fā)送或者接收消息的應用程序直接交互。然而，也有一些特殊的隊列管理器發(fā)揮了路由器或者中繼器的作用：他們將輸入的消息轉發(fā)給其他的隊列管理器。一種解決方案是，使用若干了解網(wǎng)絡拓撲的路由器。如果發(fā)送者A將目的地為B的消息放入其本地隊列中，該消息將會首先傳輸?shù)阶钹徑穆酚善?，該路由器知道如何將該消息往B的方向轉發(fā)。GeneralArchitectureofaMessage-QueuingSystem(2)隊列由隊列管理器來管理。一般來說，隊列管理器與發(fā)送或者接收消45GeneralArchitectureofaMessage-QueuingSystem(3)Thegeneralorganizationofamessage-queuingsystemwithrouters.2-29GeneralArchitectureofaMess46Stream-orientedcommunication隨著多媒體分布式系統(tǒng)的出現(xiàn)，必須引入流（stream）的概念，以支持連續(xù)媒體的通信。-Datastream-Qualityofservices-StreamsynchronizationStream-orientedcommunication隨47DataStreamAdatastreamisasequenceofdataunitsDiscreteorcontinuous:-Discretestream:UNIXpipesorTCP/IPconnections-Continuousstream:audioorvideo（同步非常關鍵）Forcontinuousstream,threetransmissionmodes:-Asynchronoustransmissionmode:thedataitemsaretransmittedoneaftertheother,buttherearenofurthertimingconstraintsonwhentransmissionshouldtakeplace-Synchronoustransmissionmode:thereisamaximumend-to-enddelaydefinedforeachunitinadatastream-Isochronous（等時）

transmissionmode:dataunitsaretransferredontime,haveamaximumandminimumend-to-enddelayDataStreamAdatastreamisa48

（a）通過網(wǎng)絡在兩個進程間建立流連接（b）在兩個設備間直接建立流連接分布式系統(tǒng)中的通信課件49ReadingMaterials

“DistributedSystems:PrinciplesandParadigms”byTanenbaumandVanSteen,PrenticeHall2002“DistributedSystems:ConceptsandDesign”byGeorgeCoulourisetc.,Addison-Wesley2001(Thirdedition)分布式系統(tǒng)設計，(美)JieWu著，高傳善等譯，機械工業(yè)出版社，2001分布式操作系統(tǒng)，AndrewS.Tanenbaum著，電子工業(yè)出版社，1999ReadingMaterials50分布式系統(tǒng)中的通信進程間通信是一切分布式系統(tǒng)的核心。分布式系統(tǒng)中的通信都是基于底層網(wǎng)絡提供的低層消息傳遞機制的。通過消息傳遞來描述通信過程比使用基于共享存儲器的原語來描述要更困難。分布式系統(tǒng)中的通信進程間通信是一切分布式系統(tǒng)的核心。514種廣泛使用的通信模型遠程過程調用（remoteprocedurecall,RPC）遠程方法調用（remotemethodinvocation,RMI）面向消息的中間件（message-orientedmiddleware,MOM）面向流的通信（stream-orientedcommunication）4種廣泛使用的通信模型52CommunicationProtocols

由于沒有共享存儲器，分布式系統(tǒng)中的所有通信都是基于（低層）消息交換的。Protocolsareagreements/rulesoncommunicationProtocolscouldbeconnection-orientedorconnectionlessApplicationPresentationSessionTransportNetworkDatalinkPhysicalApplicationprotocolPresentationprotocolSessionprotocolTransportprotocolNetworkprotocolDatalinkprotocolPhysicalprotocolNetwork7654321CommunicationProtocols由于沒53LayeredProtocolsAtypicalmessageasitappearsonthenetwork.2-2LayeredProtocolsAtypicalmes54DataLinkLayerDiscussionbetweenareceiverandasenderinthedatalinklayer.2-3DataLinkLayerDiscussionbetw55Client-ServerInteractionusingTCPNormaloperationofTCP(常規(guī)TCP的許多開銷都耗費在連接的管理上).TransactionalTCP(更經濟的方式).2-4服務器執(zhí)行請求的操作告訴服務器關閉該連接客戶啟動連接建立過程1,2,3要求客戶釋放連接將發(fā)送請求當作連接的建立標志(一個消息包含三條信息)把送回結果當作連接的關閉標志確認連接的終止確認已收到客戶的請求Client-ServerInteractionusin56MiddlewareProtocolsMiddleware:-Anapplicationthatlogicallylivesintheapplicationlayer-Containsmanygeneral-purposeprotocolsthatwarrant（代表）

theirownlayers-(會話層和表示層由一個單一的中間件層代替)ApplicationMiddlewareTransportNetworkDatalinkPhysicalApplicationprotocolMiddlewareprotocolTransportprotocolNetworkprotocolDatalinkprotocolPhysicalprotocolNetwork654321MiddlewareProtocolsMiddleware57Client-ServerCommunicationModelStructure:groupofserversofferingservicetoclients-Servers:offerservicestotheuserscalled“clients”-Clients:applicationsrequiringservicesfromservers-Example:WebServer/clients,Fileserver…Whyuseclient-servermodel-simplicity-low(er)overheadsclientkernelfileserverkernelprocessserverkernelterminalserverkernelClient-ServerCommunicationMo58Client-ServerCommunicationModelBasedonarequest/responseparadigm-Clientssendarequestaskingforservice(e.g.,afileblock)-Serverprocessesandreplieswithresult(orerror)Techniques:-Socket,RemoteProcedureCalls(RPC),RemoteMethodInvocation(RMI)

clientkernelfileserverkernelprocessserverkernelterminalserverkernelClient-ServerCommunicationMo59RemoteProcedureCall(RPC)Client-ServerprovidesamechanismforservicesindistributedsystemsBUT-requiresexplicitcommunication(send-receive)Q:Howdowemake“distributedcomputinglookliketraditional(centralized)computing”?Canweuseprocedurecalls?AcallsB->Asuspended,Bexecutes->Breturns,Aexecutes

?InformationfromA(caller)toB(callee)transferredusingparameters

?SomewhateasiersincebothcallerandcalleeexecuteinthesameaddressspaceRemoteProcedureCall(RPC)Cli60ConventionalProcedureCallParameterpassinginalocalprocedurecall:thestackbeforethecalltoread(fd,buf,nbytes)Thestackwhilethecalledprocedureisactive(執(zhí)行時)調用方(主程序)把參數(shù)、返回地址反序壓入堆棧ConventionalProcedureCallPar61RPCInDistributedsystems:thecalleemaybeonadifferentsystem

-RemoteProcedurecall(RPC,允許程序調用位于其它機器上的進程)-NOEXPLICITMESSAGEPASSING（對編程人員）

從而達到隱藏通信（send和receive），實現(xiàn)分布式系統(tǒng)中的訪問透明性Goal:MakeRPClook(asmuchaspossible)likelocalprocedurecall

-allowremoteservicestobecalledasprocedures-callershouldnotbeawareofthefactthatthecalleeis(executing)onadifferentmachine(orviceversa)Althoughnomessagepassing(atuserlevel),parametersmuststillbepassed&resultsmuststillbereturned!RPCInDistributedsystems:the62ClientandServerStubsPrincipleofRPCbetweenaclientandserverprogram.

客戶通過執(zhí)行普通的（本地）過程調用來訪問遠程服務，它并不需要直接調用Send和Receive，消息傳遞的所有細節(jié)都隱藏在雙方的庫過程（Stub,Skeleton）中。ClientandServerStubs63StepsofaremoteprocedurecallClientprocedurecallsclientstubinnormalwayClientstubbuildsmessage,callslocalOSClient’sOSsendsmessagetoremoteOSRemoteOSgivesmessagetoserverstubServerstubunpacksparameters,callsserverServerdoeswork,returnsresulttothestubServerstubpacksitinmessage,callslocalOSServer’sOSsendsmessagetoclient’sOSClient’sOSgivesmessagetoclientstubStubunpacksresult,returnstoclientStepsofaremoteprocedureca64PassingValueParameters(1)StepsinvolvedindoingremotecomputationthroughRPC2-8PassingValueParameters(1)2-65PassingValueParameters(2)Problem:differentmachineshavedifferentdataformats-Intel:littleendian,SPARC:bigendianSolution:useastandardrepresentation-Example:externaldatarepresentation(XDR)PassingValueParameters(2)Pr66Marshalling:ReferenceParametersProblem:howdowepasspointers?

（指針只在它被使用的進程的地址空間里面是有意義的）-Ifitpointstoawell-defineddatastructure,passacopytotheserverandtheserverstubpasses（使用）

apointertothelocalcopy

(來調用服務器程序）Whataboutdatastructurescontainingpointers?-Prohibit-Copy/restore,

machineindependentrepresentationCallbyCopy/restore:

首先由調用者將變量拷貝到Stack，調用完成之后，將堆棧中的變量復制回去覆蓋調用方該變量原先的值。參數(shù)從客戶發(fā)送到服務器，在那里修改，然后發(fā)送回客戶，覆蓋原來的值。

Marshalling（編組，即把參數(shù)打包進消息中發(fā)送到服務器）:transformparameters/resultsintoabytestreamMarshalling:ReferenceParamet67BindingProblem:howdoesaclientlocateaserver?

（Client要發(fā)送消息到服務器，它需要知道服務器的地址）-UseBindingsServer-Exportserverinterfaceduringinitialization-Sendname,version#,uniqueidentifier,handle(address)tobinderClient(第一次調用遠程過程，還沒有綁定到一個Server）-FirstRPC:sendmsgtobindertoimportserverinterface-Binder:checktoseeifsomeserverhasexportedtheinterface

?ReturnhandleanduniqueidentifiertoclientBinder充當一個注冊服務器的角色。BindingProblem:howdoesacli68Binding:CommentsMethodflexible-canhandlemultipleserverswithsameinterface-bindercanpollaservertoseeifitisupandmayderegisteritifitisdownforfaulttolerance-canenforceauthentication(notgivinginterfacetousernotonlist)ExportingandimportingincursoverheadsBindercanbeabottleneck-UsemultiplebindersBindercandoloadbalancing

隨機地擴展（散播）Clients到這些Servers來平衡負載。Binding:CommentsMethodflexib69AsynchronousRPC(1)TheinterconnectionbetweenclientandserverinatraditionalRPCTheinteractionusingasynchronousRPC2-12AsynchronousRPC(1)Theinterc70AsynchronousRPC(2)AclientandserverinteractingthroughtwoasynchronousRPCs2-13AsynchronousRPC(2)2-1371WritingaClientandaServerThestepsinwritingaclientandaserverinDCERPC.2-14WritingaClientandaServerT72BindingaClienttoaServerClient-to-serverbindinginDCE.2-15BindingaClienttoaServer2-73RemoteMethodInvocation(RMI)RPCsappliedto(distributed)objects,i.e.,instancesofaclass-Class:object-orientedabstraction;modulewithdataandoperations-Separationbetweeninterfaceandimplementation-Interfaceresidesononemachine,implementationonanotherRMIssupportsystem-wideobjectreferences-ParameterscanbeobjectreferencesRemoteMethodInvocation(RMI)74DistributedObjectsWhenaclientbindstoadistributedobject,loadtheinterface(“proxy”)intoclientaddressspace-ProxyanalogoustostubsServerstubisreferredtoasaskeletonClientOSClientinvokesamethodClientServerOSSkeletonServerStateMethodInterfaceProxySkeletoninvokessamemethodatobjectSameinterfaceasobjectClientmachineServermachineObjectNetworkMarshalledinvocationispassedacrossnetworkDistributedObjectsClientOSCl75ProxiesandSkeletonsProxy:clientstub-MaintainsserverID,endpoint,objectID-Setsupandtearsdownconnectionwiththeserver-Doesserializationoflocalobjectparameters-Inpractice,canbedownloaded/constructedontheflySkeleton:serverstub-DoesdeserializationandpassesparameterstoserverandsendsresulttoproxyProxiesandSkeletonsProxy:cl76BindingaClienttoanObjectAnexamplewithimplicitbindingusingonlyglobalreferencesAnexamplewithexplicitbindingusingglobalandlocalreferencesDistr_object*obj_ref; //Declareasystemwideobjectreference

obj_ref=…; //Initializethereferencetoadistributedobject

obj_ref->do_something(); //Implicitlybindandinvokeamethod (a)Distr_objectobjPref; //Declareasystemwideobjectreference

Local_object*obj_ptr; //Declareapointertolocalobjects

obj_ref=…; //Initializethereferencetoadistributedobject

obj_ptr=bind(obj_ref); //Explicitlybindandobtainapointertothelocalproxy

obj_ptr->do_something(); //Invokeamethodonthelocalproxy (b)BindingaClienttoanObjectA77ParameterPassingThesituationwhenpassinganobjectbyreferenceorbyvalue.2-18ParameterPassingThesituation78TheDCEDistributed-ObjectModelDistributeddynamicobjectsinDCE.Distributednamedobjects2-19TheDCEDistributed-ObjectMod79面向消息的通信遠程過程調用和遠程對象調用都有助于隱藏分布式系統(tǒng)中的通信，也就是說增強了訪問透明性。不幸的是，這兩種機制并不總是適用的。特別是當無法保證發(fā)出請求時接收端一定正在執(zhí)行的情況下，就必須有其他的通信服務。同時，RPC和RMI的同步特性也會造成客戶在發(fā)出的請求得到處理之前被阻塞，因而有時也需要采取其他辦法。這里所說的“其他方法”就是消息傳遞機制。面向消息的通信遠程過程調用和遠程對象調用都有助于隱藏分布式系80Message-orientedcommunication-Persistenceandsynchronicity-Message-orientedtransientcommunication

?Berkeleysocket

?MPI-Message-orientedpersistentcommunicationmessage?MessagequeuingsystemsMessage-orientedcommunication81持久通信與暫時通信持久(persistent)通信需要傳輸?shù)南⒃谔峤恢笥赏ㄐ畔到y(tǒng)來存儲，直到將其交付給接收者為止。即在將消息成功交付給下一個通信服務器之前，消息一直存儲在通信服務器中。其典型例子是電子郵件系統(tǒng)。暫時(transient)通信通信系統(tǒng)只在發(fā)送和接收消息的應用程序的運行期間存儲消息。更準確地說，如果通信服務器無法將消息遞送到下一個服務器或者接收者，消息將會被簡單地丟棄。持久通信與暫時通信持久(persistent)通信82異步通信與同步通信異步通信發(fā)送者把要傳輸?shù)南⑻峤恢罅⒓蠢^續(xù)執(zhí)行其其他程序，這意味著該消息存儲在位于發(fā)送端主機的本地緩沖區(qū)中，或者存儲在送達的第一個通信服務器上的緩沖區(qū)中。同步通信發(fā)送者在提交消息之后會被阻塞，直到消息已經到達并存儲在接收主機的本地緩沖區(qū)中以后，也就是消息確實已經傳送到接收者之后,才會繼續(xù)執(zhí)行其它程序。異步通信與同步通信異步通信83PersistenceandSynchronicity:CommentsTransientsynchronouscomm:response-based=>weakerforms,suchasdelivery-basedandreply-basedTransientasynchronouscomm:message-passingsystemsPersistentcomm:developingofmiddlewareforlarge-scaleinterconnectednetworks;failuremaskingandrecoveryPersistenceandSynchronicity:84Message-orientedTransientComm.Manydistributedsystemsbuiltontopofsimplemessage-orientedmodel-Example:Berkeleysockets-AsocketisanabstractrepresentationofacommunicationendpointPrimitiveMeaningSocketCreateanewcommunicationendpointBindAttachalocaladdresstoasocketListenAnnouncewillingnesstoacceptconnectionsAcceptBlockcalleruntilaconnectionrequestarrivesConnectAc