P. A. Felber and R. Guerraoui, The Implementation of a CORBA Group Communication Service, Theory and Practice of Object Systems 4 (1998), no. 2, 93 105.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....CORBA [12] until revision 2.4, did not provide any mechanism to handle object replication and failure management. Thus, many CORBA compliant platforms (e.g. 1] 2] 5] 6] 9] were developed to support object replication in CORBA applications. Taxonomies of these systems can be found in [3] and [6] In 1998 the OMG issued a RFP ( 10] with the aim of standardizing a result of these efforts, i.e. of defining a single standard architecture embedding some of the ideas from the previous experiences. The result is the Fault Tolerant CORBA (FT CORBA) specification [13] published in ....

P. A. Felber and R. Guerraoui, The Implementation of a CORBA Group Communication Service, Theory and Practice of Object Systems 4 (1998), no. 2, 93 105.

....are tightly coupled and must run in a partially synchronous 35 system, as asynchrony can cause the problem of system instability at the group communication level. The previous problem has even a greater impact on systems following the service approach, i.e. the Object Group Service (OGS) [49] and the NewTOP object group service [50] that build a group communication toolkit exploiting the ORB as the underlying communication channel and offer developers IDL interfaces to use such services. This implies that these toolkits are fully 40 portable and interoperable, but the developer must ....

Felber PA, Guerraoui R. The implementation of a CORBA group communication service. Theory and Practice of Object Systems 1998; 4(2):93--105. 20

....point out that even though the paper shows a FT CORBA com pliant platform as a case study, the notion of 3T replication is not related to a specific technology. computing. The main contributions to the standard definition have been given by the following systems: Isis Orbix and Electra [24] OGS [14], AQuA [11] DOORS [10] and Eternal [25] which has been the standard s proof of concept) However, such systems either do not provide replica consistency (e.g. DOORS) or to provide it they adopt the approach of relaying requests to replicas using group toolkits (e.g. Electra, AQuA, Eternal) ....

P. A. Felber and R. Guerraoui. The Implementation of a CORBA Group Communication Service. Theory and Practice of Object Systems, 4(2):93 105, 1998.

....point out that even though the paper shows a FT CORBA compliant platform as a case study, the notion of 3T replication is not related to a specific technology. computing. The main contributions to the standard definition have been given by the following systems: Isis Orbix and Electra [24] OGS [14], AQuA [11] DOORS [10] and Eternal [25] which has been the standard s proof of concept) However, such systems either do not provide replica consistency (e.g. DOORS) or to provide it they adopt the approach of relaying requests to replicas using group toolkits (e.g. Electra, AQuA, Eternal) ....

P. A. Felber and R. Guerraoui. The Implementation of a CORBA Group Communication Service. Theory and Practice of Object Systems, 4(2):93--105, 1998.

....until revision 2.4, did not provide any mechanism to handle replication and failure management CORBA based applications. Thus, many CORBA compliant platforms (e.g. 1] 3] 4] 7] 8] 10] were developed to support replication of CORBA objects. Taxonomies of these systems can be found in [5] and [8] In 1998 the OMG issued a RFP ( 12] whose aim was to standardize the results of these efforts, defining a single standard architecture that incorporates some of the ideas from the previous experiences. The result is the Fault Tolerant CORBA (FT CORBA) specification [13] published in ....

P. A. Felber and R. Guerraoui, The Implementation of a CORBA Group Communication Service, in Theory and Practice of Object Systems, vol. 4, no. 2, pp. 93-105, 1998.

....3 services usually requests visibility of topology and locality information. In addition, CORBA implementations lack abstractions for managing object groups, even if the collection abstraction is clearly necessary for the management of replicated services [18, 19]. Finally, the interaction of objects using diverse security technologies is complex because CORBA does not standardize the possibility to negotiate security technology [20] Other proposals abstract from implementation technologies and describe solution frameworks at the architecture level. The ....

P. Felber, R. Guerraoui, and A. Schiper, "The Implementation of a CORBA Group Communication Service", Theory and Practice of Object Systems, Vol. 4, No. 2, 1998.

....while managing distributed resources and services usually request visibility of topology and locality information. In addition, CORBA implementations lack abstractions for managing object groups, even if the collection abstraction is clearly necessary for the management of replicated services [29], 30] Finally, the interaction of objects using diverse security technologies is complex because CORBA does not standardize the possibility to negotiate security technology [31] Other proposals are abstracted from implementation technologies and describe solution frameworks at the architecture ....

P. Felber, R. Guerraoui, and A. Schiper, "The implementation of a CORBA group communication service," Theory Practice Object Systems, vol. 4, no. 2, 1998.

....CORBA [12] until revision 2.4, did not provide any mechanism to handle object replication and failure management. Thus, many CORBA compliant platforms (e.g. 1] 2] 5] 6] 9] were developed to support object replication in CORBA applications. Taxonomies of these systems can be found in [3] and [6] In 1998 the OMG issued a RFP ( 10] with the aim of standardizing a result of these e orts, i.e. of de ning a single standard architecture embedding some of the ideas from the previous experiences. The result is the Fault Tolerant CORBA (FT CORBA) speci cation [13] published in early ....

P. A. Felber and R. Guerraoui, The Implementation of a CORBA Group Communication Service, Theory and Practice of Object Systems 4 (1998), no. 2, 93-105.

....of tasks, and . support of several different data dispatching strategies in order to allow different computing algorithms and to improve network traffic (compared to sending the complete data to each worker) The notion of a CORBA based Object Group Service was first introduced by Felber ( 2] [3]) However, while the OGS in Felber s approach serves for supporting replication scenarios, the application purpose of our OGS is totally different, because it aims at facilitating the parallel processing of CORBA operation calls. With the help of the OGS, a request issued by a master can be ....

....with the selected strategy. send data to group 1 Group g1 = grpman.resolve( SERVERPOOL1 ) org.omg.CORBA.Any data = orb.create any( int[ vec1 = 1, 2, 3, 4, 5, 6, 7, 8, 9 ; l arrayHelper data helper = new l arrayHelper( data helper.insert(data,vec1) int[ lenSeq = new int[3]; lenSeq[0] 3; lenSeq[1] 0; lenSeq[2] 2; DataStructure message = new DataStructure( DataDispatchStrategy.DIFFERENT SIZE, lenSeq,0,any) g1.send(message, master) send data to group 2 Group g2 = grpman.resolve( SERVERPOOL2 ) int[ vec2 = 10, 20, 30, 40, 50, 60, 70, 80, 90 ; ....

Felber, P., Guerraoui R., Schiper A. (1998): "The implementation of a CORBA group communication service"; in: Theory and Practice of Object Systems, vol. 4, no. 2, pp. 93-105

....a restriction of the scope of the OGS to core functionality, and . Generality of functionality by abstraction from specific data structures in order to make the service suitable for a great variety of tasks. The general idea of a CORBA based Object Group Service traces back to the work of Felber [2] who has suggested this approach for use in replication scenarios. As opposed to this application purpose, our design and the resulting implementation aim at sup porting the parallel processing of CORBA operation calls, i.e. a request issued by a master is propagated to any number of workers in ....

Felber, P., Guerraoui R., Schiper A. (1998): "The implementation of a CORBA group communication service"; in: Theory and Practice of Object Systems, vol. 4, no. 2, pp. 93-105

....of the scope of the OGS to core functionality, and . Generality of functionality by abstraction from specific data structures in order to make the service suitable for a great variety of tasks. The general idea of a CORBA based Object Group Service traces back to the work of Felber ( 3] [4]) who has suggested this approach for use in replication scenarios. As opposed to this application purpose, our design and the resulting implementation aim at supporting the parallel processing of CORBA operation calls, i.e. a request issued by a master is propagated to any number of workers in ....

Felber, P., Guerraoui R., Schiper A. (1998): "The implementation of a CORBA group communication service"; in: Theory and Practice of Object Systems, vol. 4, no. 2, pp. 93-105

....CORBA is in its infancy. The limited specification that has been adopted by the OMG does not address yet al..l the strong fault tolerance requirements of mission critical applications. Current research on fault tolerant CORBA has focussed on using object group communication mechanisms [3, 8, 10] to replicate the critical objects of each application. These engines maintain the consistency of all members of a group of replicated objects by providing reliable delivery of messages among all the replicas. The mechanism is straightforward but it cannot handle network partitions without using ....

P. A. Felber and R. Guerraoui, "The Implementation of a CORBA Group Communication Service," Theory and Practice of Object Systems, vol. 4, no. 2, pp. 93-105, 1998.

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