Specification and management of extended transactions in a programmable transaction environment

A Transaction Specification and Management Environment (TSME) is a transaction processing system toolkit that supports the definition and construction of application-specific extended transaction models (ETMs). The TSME provides a transaction specification language that allows a transaction model designer to create implementation-independent specifications of extended transactions. In addition, the TSME provides a programmable transaction management mechanism that assembles and configures a run-time environment to support specified ETMs. The authors discuss the TSME in the context of a distributed object management system (DOMS), and describe specifications of extended transactions and corresponding configurations of transaction management mechanisms.<<ETX>>

[1]  Ahmed K. Elmagarmid,et al.  A Multidatabase Transaction Model for InterBase , 1990, VLDB.

[2]  Barbara Liskov,et al.  Distributed programming in Argus , 1988, CACM.

[3]  Mark F. Hornick,et al.  An environment for the specification and management of extended transactions in DOMS , 1993, Proceedings RIDE-IMS `93: Third International Workshop on Research Issues in Data Engineering: Interoperability in Multidatabase Systems.

[4]  Christos H. Papadimitriou,et al.  The Concurrency Control Mechanism of SDD-1: A System for Distributed Databases (The Fully Redundant Case) , 1978, IEEE Transactions on Software Engineering.

[5]  Nancy A. Lynch,et al.  Multilevel atomicity—a new correctness criterion for database concurrency control , 1983, TODS.

[6]  Hector Garcia-Molina,et al.  Coordinating activities through extended sagas: a summary , 1991, COMPCON Spring '91 Digest of Papers.

[7]  Maurice Herlihy,et al.  Apologizing versus asking permission: optimistic concurrency control for abstract data types , 1990, TODS.

[8]  Umeshwar Dayal,et al.  A Transactional Model for Long-Running Activities , 1991, VLDB.

[9]  B. R. Badrinath,et al.  Semantics-based concurrency control: Beyond commutativity , 1987, 1987 IEEE Third International Conference on Data Engineering.

[10]  Sandra Heiler,et al.  Distributed Object Management , 1992, Int. J. Cooperative Inf. Syst..

[11]  Alejandro P. Buchmann,et al.  A Transaction Model for Active Distributed Object Systems , 1992, Database Transaction Models for Advanced Applications.

[12]  Panos K. Chrysanthis,et al.  ACTA: The SAGA Continues , 1992, Database Transaction Models for Advanced Applications.

[13]  William E. Weihl,et al.  Commutativity-based concurrency control for abstract data types , 1988, [1988] Proceedings of the Twenty-First Annual Hawaii International Conference on System Sciences. Volume II: Software track.

[14]  Umeshwar Dayal,et al.  Organizing long-running activities with triggers and transactions , 1990, SIGMOD '90.

[15]  Amit P. Sheth,et al.  Specifying and Enforcing Intertask Dependencies , 1993, VLDB.

[16]  William E. Weihl,et al.  Local atomicity properties: modular concurrency control for abstract data types , 1989, TOPL.

[17]  Abraham Silberschatz,et al.  On Rigorous Transaction Scheduling , 1991, IEEE Trans. Software Eng..

[18]  Amit P. Sheth,et al.  On serializability of multidatabase transactions through forced local conflicts , 1991, [1991] Proceedings. Seventh International Conference on Data Engineering.

[19]  Panos K. Chrysanthis,et al.  ACTA: a framework for specifying and reasoning about transaction structure and behavior , 1990, SIGMOD '90.

[20]  Panos K. Chrysanthis,et al.  In Search of Acceptability Citeria: Database Consistency Requirements and Transaction Correctness properties , 1992, IWDOM.

[21]  Hector Garcia-Molina,et al.  Using semantic knowledge for transaction processing in a distributed database , 1983, TODS.

[22]  M. Tamer Özsu,et al.  Using semantic knowledge of transactions to increase concurrency , 1989, TODS.