Object-Based Synchronization and Recovery

Get BibTex-formatted data

Author

James E. Allchin; Martin S McKendry

Entry type

techreport

Abstract

Using abstratct data types and nested actions as system structuring tools can help create more robust systems using these tools, several interesting principles have been encountered. First, in this environment synchronization and recovry should be associated with each object. By associating synchronization with each object and by using the semantics of the obeject operations, it is possible to acheieve higher concurrency. Binding recovery to ojects permits efficient recovery techniques which might not be possible without the specific implementation knowledge available to the programmer of the object. Second, its important to distinguish between the abstract behavior of an object and its implementation when analyzing cincurrency. Third, using serializability for the abstact behavior of an object is sometimes undesirable or unnecessary. Whether an object provides serializability as the abstarct behavior depends on the semantics of how the object is used. Examples of object types which motivate the principles are presented.

Key alpha

Allchin

Note

September 1982

School

Georgia Insititute of Technology

Publication Date

2001-01-01

1. Inroduction 2. Objects and actions 3. Abstract vs. Implementation Behavior 4. Weak Abstract Behavior and General Synchronization Requirements 5. Recovery Support 6. Guaranteeing Progress 7. Permanent Action Disributed Commitment 8. Summary Acknowedgements Appendix A: A storage map object example References

Location

A hard-copy of this is in the Papers Cabinet

Subject

Object Based Synchronization and Recovery

BibTex-formatted data

To refer to this entry, you may select and copy the text below and paste it into your BibTex document. Note that the text may not contain all macros that BibTex supports.

@Techreport{ Allchin,
	title = "Object-Based Synchronization and Recovery",
	author = "James E. Allchin; Martin S McKendry",
	note = "September 1982",
	school = "Georgia Insititute  of Technology",
	abstract = "Using abstratct data types and nested actions as system structuring tools can help create more robust systems using these tools, several interesting principles have been encountered. First, in this environment synchronization and recovry should be associated with each object. By associating synchronization with each object and by using the semantics of the obeject operations, it is possible to acheieve higher concurrency. Binding recovery to ojects permits efficient recovery techniques which might not be possible without the specific implementation knowledge available to the programmer of the object. Second, its important to  distinguish between the abstract behavior of an object and its implementation when analyzing cincurrency. Third, using serializability for the abstact behavior of an object is sometimes undesirable or unnecessary. Whether an object provides serializability as the abstarct behavior depends on the semantics of how the object is used. Examples of object types which motivate the principles are presented.",
	contents = "1. Inroduction
2. Objects and actions
3. Abstract vs. Implementation Behavior
4. Weak Abstract Behavior and General                                      
   Synchronization Requirements
5. Recovery Support
6. Guaranteeing Progress
7. Permanent Action Disributed
   Commitment
8. Summary
Acknowedgements
Appendix A: A storage map object example
References",
	subject = "Object Based Synchronization and Recovery",
}