Abstract. In this paper we present a new infrastructure for building distributed applications that communicate through remote objects. The objects are available by the use of the Java RMI, enhanced by replication. Shared objects may be arbitrary complex wi
severaltimesbyitscalleethatisalsoreplicated.Thesystemshouldeitherde-tectsuchrepeatedcallsandsilentlyignorethem,oravoidthembyignoringsomecallsattheirsource.RRMIsolvetheprobleminaslightlydi erentmanner.Be-causeofthereplicationstrategy,theobjectsarecalleddirectlybytheclientonlyonce.Suchcallsarethentransmittedtoreplicas,butthere-executionisexplicit,thereforemaybetreateddi erently—itisjustnotreplicated.Theonlymethodinvocationsthatarereplicatedcomedirectlyfromtheuser.Wheneveranestedmethodiscalledbyasharedobject,itisexecutedonlyonlocallyavail-ablereplicaofthatobject.Suchnestedcallsarenotregisteredinthehistory,andarenotreplicated.Thisassumesthateverysharedobjectreachablethroughremotereferencesisavailablelocally.
Naming.InstandardRMI,objects,beforetheycanbeaccessed,areboundtoanamewithinaregistry.Registryisasimplenamingservicethatholdsanarrayofobjects’stubs,andsendsthemtoclientswhentheyissuelookupoperation.Thestubinternallycontainsenoughinformationtolocatetheserverthatpro-videstheobjectimplementation,i.e.itsaddressandportnumber.Thestandardimplementationdoesnotassumereplication,soeveryobjectisregisteredonlyonce,attheserverthatprovidesitsimplementation.Inanenvironmentsupport-ingreplicationtheregistryisawareofobjectreplicasandreturnsstubspointingtothenearestserver.“Near”maybede neddi erently:basedonthenetworkdelay,latencies,serverload,andotherfactors.
Theprocessofobjectcreationandregistrationneedstobedoneatomicallyinordertoavoidcon ictingnameresolutionsatdi erentservers.Theseoperationsareintegratedwithintheconsistencymanagement.Successfulobjectcreationguaranteesthattherewasnootherobjectwithagivennamebeforethatcreation.Remotereferencesmaybepassedbyvaluebetweensharedobjectsasmethodparameters.Whensuchareferenceistransferedtoanotherserver,itsrepresen-tationisupdatedtopointtothatserver,iftheserverholdsareplicaofthatobject.Thisisnecessarytoproperlyhandlenestedcalls:itwasassumedthatreplicasofobjectsthatarereferencedareavailablelocally,atthesameserver.Replicationdomains.ObjectsinRRMIareallowedtocallmethodsofotherob-jectsbecausetheyareexpectedtobeavailablelocally.Intheworstcase,whenthereissomekindoflinkbetweeneveryobjectinthesystem,theassumptionwillrequiretotalreplicationofallobjects.Obviouslythisdoesnotleadtoop-timale ciency,becausesomereplicaswillbeupdatedevenwhentheyarenotaccessedbyanyone.Weintroduceanewconceptofreplicationdomains[10]inordertoalleviatetheproblem.Areplicationdomainessentiallyisasetofsharedobjectsthatmayreferenceeachother,andasetofserversthatmaintaintheirreplicas.Therearenoreferencesbetweenobjectsfromdi erentdomains.Objectsfromdi erentdomainsmaybereplicatedonadi erentsetofservers.Thecon-ceptre ectsdi erentrequirementsofconcurrentapplicationsthatrunontopofRRMI.Applicationshavedi erentexpectationsconcerningobjectsavailability,andtheirconsistencymanagement.Theprogrammerisresponsibleforde ningreplicationdomainsandobjects’associationstodomains.
Method Invocation presen... 暂无评价 24页 免费 A Concept of Replicated ... 暂无评价 8页 免费 REMOTE EQUIPMENT AS D... 3页 免费 On the combination...
A Concept of Replicated ... 暂无评价 8页 免费 REMOTE EQUIPMENT AS D..... Compiler Optimized Remote Method Invocation Ronald Veldema Michael Philippsen ...
10页 免费 A Concept of Replicated ... 暂无评价 8页 免费...J.UCS Tactics for Remote Method Invocation Fernando Magno Quint?o Pereira a...
both within local trust domains and more widely; for example, for remote method invocation or between object managers in the case of replicated or ...
both within local trust domains and more widely; for example, for remote method invocation or between object managers in the case of replicated or ...
热门文档