The CORBA activity service framework for supporting extended transactions

  • Authors:
  • I. Houston;M. C. Little;I. Robinson;S. K. Shrivastava;S. M. Wheater

  • Affiliations:
  • IBM Hursley Laboratories, Hursley, U.K.;Arjuna Technologies Ltd, Newcastle-upon-Tyne, U.K. and School of Computing Science, Newcastle University, Newcastle-upon-Tyne, U.K.;IBM Hursley Laboratories, Hursley, U.K.;School of Computing Science, Newcastle University, Newcastle-upon-Tyne, U.K.;Arjuna Technologies Ltd, Newcastle-upon-Tyne, U.K. and School of Computing Science, Newcastle University, Newcastle-upon-Tyne, U.K.

  • Venue:
  • Software—Practice & Experience - Special issue: Middleware
  • Year:
  • 2003

Quantified Score

Hi-index 0.00

Visualization

Abstract

Although it has long been realized that ACID (atomicity, consistency, isolation, durability) transactions by themselves are not adequate for structuring long-lived applications and much research work has been done on developing specific extended transaction models, no middleware support for building extended transactions is currently available and the situation remains that a programmer often has to develop application specific mechanisms. The CORBA Activity Service Framework described in this paper is a way out of this situation. The design of the service is based on the insight that the various extended transaction models can be supported by providing a general purpose event signalling mechanism that can be programmed to enable activities--application specific units of computations--to coordinate each other in a manner prescribed by the model under consideration. The different extended transaction models can be mapped onto specific implementations of this framework, permitting such transactions to span a network of systems connected indirectly by some distribution infrastructure. The framework described in this paper is an overview of the OMG's (Object Management Group) Additional Structuring Mechanisms for the OTS standard. Through a number of examples the paper shows that the framework has the flexibility to support a wide variety of extended transaction models. Although the framework is presented here in CORBA specific terms, the main ideas are sufficiently general, so that it should be possible to use them in conjunction with other middleware.