Implementing atomic objects with the RelaX transaction facility

Mock, Michael; Kroeger, Reinhold

doi:10.1109/iwooos.1991.183048

Cited by 13 publications

(5 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Other major features of Amadeus included language-independent s u p p o r t for atomic objects and transactions 14,24] based on the use of the RelaX transaction manager and libraries 11], and a novel security model supporting access control for objects at the level of individual operations as well as isolation of untrustworthy c o d e 1 7 ].…”

Section: Related Workmentioning

confidence: 99%

An overview of the Tigger object-support operating system framework

Cahill

1996

SOFSEM'96: Theory and Practice of Informatics

View full text Add to dashboard Cite

Abstract. This paper describes the motivations for and main features of Tigger { a framework for the construction of a family of object-support operating systems that can be tailored for use in a variety of di erent application domains. An important goal of the design of Tigger is that instantiations of the framework should be able to support (a number of) di erent object models in order to allow a range of object-oriented languages for distributed or persistent programming to be supported without unnecessary duplication of e ort. A further goal of the design is that instantiations of the framework should be able to support the same object model in di erent w ays depending on the requirements of the applications to be supported by t h o s e i n s t a n tiations. This paper describes the main features of the Tigger framework that allow t h e s e goals to be realised.

show abstract

Section: Related Workmentioning

confidence: 99%

An overview of the Tigger object-support operating system framework

Cahill

1996

SOFSEM'96: Theory and Practice of Informatics

View full text Add to dashboard Cite

show abstract

“…Other major features of Amadeus included language-independent support for atomic objects and transactions 14,24] based on the use of the RelaX transaction manager and libraries 11], and a novel security model supporting access control for objects at the level of individual operations as well as isolation of untrustworthy code 17].…”

Section: Related Workmentioning

confidence: 99%

SOFSEM'96: Theory and Practice of Informatics

1996

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. This paper describes the motivations for and main features of Tigger { a framework for the construction of a family of object-support operating systems that can be tailored for use in a variety of di erent application domains. An important goal of the design of Tigger is that instantiations of the framework should be able to support (a number of) di erent object models in order to allow a range of object-oriented languages for distributed or persistent programming to be supported without unnecessary duplication of e ort. A further goal of the design is that instantiations of the framework should be able to support the same object model in di erent ways depending on the requirements of the applications to be supported by those instantiations. This paper describes the main features of the Tigger framework that allow these goals to be realised.

show abstract

“…Since in most of existing object-based distributed systems (Guerraoui et al, 1992;Herlihy et al, 1987;Mock et al, 1992;Parrington et al, 1988;Weihl, 1990), atomic objects assume particular GSPs (static, dynamic, or hybrid), their compatibility is limited. In this article we propose a way to specify atomic objects so that they do not assume any particular GSP: they are compatible with any other atomic object.…”

Section: The Incompatibility Problemmentioning

confidence: 99%

Modular Atomic Objects

Guerraoui

1995

Theory & Prac Object Systems

View full text Add to dashboard Cite

A worthwhile approach to achieve transaction atomicity within object‐based distributed systems is to confine concurrency control and recovery mechanisms within the shared objects themselves. Such objects, called atomic objects, enhance their modularity and can increase transaction concurrency. Nevertheless, when designed independently, atomic objects can be incompatible, and if combined, do not ensure transaction atomicity anymore. It has been shown that atomic objects can be incompatible when they assume different Global Serialization Protocols (GSPs). We deal with the incompatibility problem by introducing a property of atomic object specifications, named o‐atomicity, which is orthogonal to the GSP. Objects that guarantee this property achieve transaction atomicity, whatever the GSP may be. Such objects are compatible, not only with each others, but also with atomic objects that guarantee previously defined GSP‐dependent properties, i.e. static atomicity, dynamic atomicity or hybrid atomicity. This is very desirable since most of existing object‐based distributed systems rely on these properties. To show how o‐atomicity can be ensured, we propose a generic implementation within an object‐oriented framework, which we illustrate through a simple banking application.

show abstract

Implementing atomic objects with the RelaX transaction facility

Cited by 13 publications

References 16 publications

An overview of the Tigger object-support operating system framework

An overview of the Tigger object-support operating system framework

SOFSEM'96: Theory and Practice of Informatics

Modular Atomic Objects

Contact Info

Product

Resources

About