Loosely Coupled Remote Invocation Mechanism And Realization

Along with the development of computer network technology and distributed application going deep into use, it is vendor's impending demand to cooperate among the different hosts in the net, and access the service and data in others. And remote invocation mechanism is more and more popular to achieve these demands.The final aim for software design is to make it loose coupling, which shows more important in remote invocation system. If we loosen the coupling between the provider and Requester, it will make the service developers' role more clear and there is no need for one to consider the other design. All of these will depress the developing difficulty. Another merit is that reducing the dependence of platform such as operating system, CPU type and programming language will make the service build up more flexibly in the system.In this paper we compare the different kinds of coupling degree in several remote invocation mechanisms, and analyze their advantage and disadvantage. I design the scheme to loosen the remote invocation coupling from four aspects, and show how to achieve these coupling.The first means is detecting the service interface and implement method. I use the state invocation protocol, in which we use IDL to describe the service interface. The change on service implement method will not affect the client' s call.;The second aspect is depressing the dependence on service settling environment. We show and compare two crossing platform skill, and complete the simple method of distinguish OS by combining the manual division and code apperception, which will reduce the developing difficulty.The third aspect is to complete the asynchrony invocation to depressing the dependence of provider and requester. We provide the callbackThe fourth aspect is to complete service's take-over to loosen the system coupling. The main skill is relocation and 'monitor heartbeat' .At last, we show the future work to further loosening system coupling.