Y.-M. Huang and C. V. Ravishankar. Designing an agent synthesis system for cross-rpc communication. IEEE Transactions on Software Engineering, 20(3):188--198, March 1994.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....RPC systems cannot be interconnected directly. Typical solutions to this problem are: 1. Black protocol boxes: protocols used by RPC programs are left as black boxes in compiling time, and are dynamically determined in binding time [2] 2. Special interfaces [23] or RPC agent synthesis systems [11] for cross RPC communications. However, one issue is still outstanding in building RPC systems for open distributed systems: the fault tolerance features. An open distributed system consists of many hardware software components that are likely to fail eventually. In many cases, such failures may ....

....and can maintain continuous computation, but the ISIS toolkit is big and relatively complex to use. Typical solutions to the cross protocol communication in RPC systems are the black protocol boxes of the HRPC [2] the special protocol conversion interface [23] and the RPC agent synthesis system [11] for cross RPC communications. The HRPC system defines five RPC components: the stub, the binding protocol, the data representation, the transport protocol, and the control protocol. An HRPC client or server and its associated stub can view each of the remaining components as a black box. These ....

[Article contains additional citation context not shown here]

Y.-M. Huang and C. V. Ravishankar. Designing an agent synthesis system for cross-rpc communication. IEEE Transactions on Software Engineering, 20(3):188--198, March 1994.

....In contrast with our emphasis on modularizing along the lines of abstract properties, however, that paper describes a more syntactic scheme based on functional components of an RPC service implementing one chosen semantics. The work on an agent synthesis system for Cross RPC communication in [11] is relatively closely related to our goals. Although the primary goal in [11] is to allow heterogeneous RPC systems to communicate with one another, the system also offers the possibility for designing and prototyping new variants of RPC. In this paper, the authors divide RPC semantics into three ....

....properties, however, that paper describes a more syntactic scheme based on functional components of an RPC service implementing one chosen semantics. The work on an agent synthesis system for Cross RPC communication in [11] is relatively closely related to our goals. Although the primary goal in [11] is to allow heterogeneous RPC systems to communicate with one another, the system also offers the possibility for designing and prototyping new variants of RPC. In this paper, the authors divide RPC semantics into three components: call semantics (synchronous versus asynchronous) failure ....

Y.-M. Huang and C. Ravishankar. Designing an agent synthesis system for cross-RPCcommunication. IEEETransactions on Software Engineering, 19(3):188--198, Mar 1994.

....model. Differences between existing protocols are either dependent on the Rpc semantics or independent if they solely relate to implementation details such as management of distributed system heterogeneity. Only the specifics related to the Rpc semantics are of interest here. Following [11], Rpc protocols can be classified according to the synchronization, failure, and topological semantics they implement. It follows that properties stated by the current Aster property tree relate to these semantics. Given the Aster property tree, the application programmer can specify the ....

Y. M. Huang and C. V. Ravishankar, "Designing an agent synthesis system for cross-rpc communication," IEEE Transactions on Software Engineering, vol. 20, no. 3, pp. 188--198, 1994.

....In contrast with our emphasis on modularizing along the lines of abstract properties, however, that paper describes a more syntactic scheme based on functional components of an RPC service implementing one chosen semantics. The work on agent synthesis system for Cross RPC communication in [HR94] is relatively closely related to our goals. Although the primary goal in [HR94] is to allow heterogeneous RPC systems to communicate with one another, the system also offers the possibility for designing and prototyping new variants of RPC. In this paper, the authors divide RPC semantics into ....

....properties, however, that paper describes a more syntactic scheme based on functional components of an RPC service implementing one chosen semantics. The work on agent synthesis system for Cross RPC communication in [HR94] is relatively closely related to our goals. Although the primary goal in [HR94] is to allow heterogeneous RPC systems to communicate with one another, the system also offers the possibility for designing and prototyping new variants of RPC. In this paper, the authors divide RPC semantics into three components: call semantics (synchronous versus asynchronous) failure ....

Y-M. Huang and C. Ravishankar. Designing an agent synthesis system for cross-RPC communication. IEEE transactions on software engineering, 19(3):188--198, Mar 1994.

....related to Schooner s RPC mechanism. These other RPC schemes have features such as external data representations, specification languages, and stub compilers [4, 7, 28, 33] Several of these systems also emphasize heterogeneity, including Matchmaker [22] Horus [14] HRPC [6] and Cicero Nestor [21]. The primary distinction between this work and Schooner is again one of orientation: the main aim of these systems is to support interprocess communication for client server style operating system services rather than application level programs. 6. Conclusion The use of the meta computation ....

Y. Huang and C. V. Ravishankar. Designing an agent synthesis system for cross-RPC communication. IEEE Transactions on Software Engineering 20, 3 (March 1994), 188198.

....been used to construct group RPC services with customizable service properties such as ordering, uniqueness, orphan handling, and bounded termination [HS95, BS95] but no support for customization of failure model. An approach for RPC customization based on specification languages is presented in [HR94] Finally, the x kernel has been used to construct highly modular, but not configurable, RPC services [HPOA89] 6 Conclusions The choice of a failure model is a key factor in determining the performance of a system, as well as its fault coverage. The approach presented in this paper makes it ....

Y-M. Huang and C. Ravishankar. Designing an agent synthesis system for cross-RPC communication. IEEE Transactions on Software Engineering, 19(3):188--198, Mar 1994.

....based on abstract properties, however, that paper describes a modularization of an RPC service implementing one chosen semantics where the modules are syntactic components rather than implementations of abstract properties. The work on an agent synthesis system for Cross RPC communication in [HR94] is relatively closely related to our goals. Although its primary goal is to allow heterogeneous RPC systems to communicate with one another, 170 the system also offers the possibility for designing and prototyping new variants of RPC. Specifically, the authors divide RPC semantics into three ....

Y-M. Huang and C. Ravishankar. Designing an agent synthesis system for cross-RPC communication. IEEE Transactions on Software Engineering, 19(3):188--198, Mar 1994.

....as to implement stronger semantics. For instance, the semantics of the base rpc mechanism of Isatis is the weakest one, that is, synchronous or asynchronous, maybe, single destination semantics. Depending on application requirements, more elaborated rpc semantics may have to be offered (e.g. see [26, 28]) In the framework of Isatis, integrating method calls based on rpcs with stronger semantics amounts to implement subclasses of the base rpc classes of Isatis. Executing different object oriented languages. Executing a given objectoriented language above Isatis requires the translation of each ....

Y. M. Huang and C. V. Ravishankar. Designing an agent synthesis system for cross-rpc communication. IEEE Transactions on Software Engineering, 20(3):188--198, 1994.

.... BN Omega Omega Omega Omega AE A A AU Theta Theta Theta Thetafl A A AU AsterProperties Rpc multiparty failure sync group result Figure 1: Aster property tree Figure 1 states nodes of the current Aster property tree whose organization follows the classification of Rpc semantics proposed in [8]. Concerning leaves definition, let us consider for illustration the Rpc failure semantics, it is associated the following leaf: exactly once, F 1 ) OE (at most once, F 2 ) OE (best effort, F 3 ) where F i and OE stand for the property s formula and the greater than relationship respectively. ....

Y. M. Huang and C. V. Ravishankar, "Designing an agent synthesis system for cross-rpc communication," IEEE Transactions on Software Engineering, vol. 20, no. 3, pp. 188--198, 1994.

....but which does not complicate verification. Our work attempts to combine these two approaches by giving programmers an executable specification language to specify control aspects of protocol execution as well as implementation details. We have implemented Cicero and used it with Nestor [9] and the URPC toolkit [10] for describing RPC protocols. Nestor is an agent synthesis and management system for synthesizing cross RPC gateway agents [11, 9] URPC (Universal RPC) is a toolkit for prototyping new RPC systems rapidly [10] Experience in these projects has shown that Cicero is ....

....language to specify control aspects of protocol execution as well as implementation details. We have implemented Cicero and used it with Nestor [9] and the URPC toolkit [10] for describing RPC protocols. Nestor is an agent synthesis and management system for synthesizing cross RPC gateway agents [11, 9]. URPC (Universal RPC) is a toolkit for prototyping new RPC systems rapidly [10] Experience in these projects has shown that Cicero is effective in implementing a variety of RPC protocols. Cicero offers a better protocol implementation paradigm with little overhead, amounting to less than 5 for ....

Y. Huang and C. V. Ravishankar. Designing An Agent Synthesis System for Cross RPC Communication. IEEE Transactions on Software Engineering, 20(3), March 1994.

....Earth Sciences Information Networking must also be implemented to interface with new RPC runtime. Even within the protocol machine implementation, a large portion of the development effort is spent at managing internal data structure and implementing low level details. According to our study [3], entire protocol machine implementation comprises only 30 to 40 of code of an RPC system, and high level protocol code accounts even less (about 10 to 15 ) As a result, much development effort has been spent on less interesting part of the RPC system This paper describes an RPC toolkit which ....

....An example given in [18] is an RPC protocol with callback. By giving programmers more control to the runtime, the URPC toolkit not only can facilitate construction of both traditional and non traditional RPCs, but also can result in a more general solution to the RPC heterogeneity problem [19, 3]. TI RPC is a transport independent RPC, which can operate on top of any available transportlayer protocols. The URPC toolkit is not only independent of transport layer protocols, but also independent of RPC semantics. The independence from RPC semantics is achieved by using a generic send receive ....

Y. Huang and C. V. Ravishankar. Designing An Agent Synthesis System for Cross RPC Communication. submitted to IEEE Transactions on Software Engineering, 1993.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC