This paper considers a class of objects, called incrementally mutable objects, that are intermediate between mutable and immutable objects. Intuitively, the only permitted modifications to an incrementally mutable object are those that add new information to the object while preserving existing information. Changes to incrementally mutable objects do not require central synchronization. When a network becomes partitioned, the same incrementally mutable object can be safely modified in each subnetwork. A mutable object can be modeled by a set of immutable objects that represent each value of the object over time and an incrementally mutable object that relates each immutable object to its successor. Multiple successors are permitted to represent parallel changes.
PDF file does not exist.
This report is related to the following area(s) of work:
Performance and DependabilityTechnical Report
CMU/SEI-87-TR-046
December 1987
SEI:
Nestor, John; Evolving Persistent Objects in a Distributed Environment (CMU/SEI-87-TR-046 ). Software Engineering Institute, Carnegie Mellon University, 1987. http://www.sei.cmu.edu/library/abstracts/reports/87tr046.cfm
IEEE:
J. Nestor, "Evolving Persistent Objects in a Distributed Environment," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical Report CMU/SEI-87-TR-046 , 1987. http://www.sei.cmu.edu/library/abstracts/reports/87tr046.cfm
APA:
Nestor, J., (1987). Evolving Persistent Objects in a Distributed Environment (CMU/SEI-87-TR-046 ). Retrieved May 21, 2013, from the Software Engineering Institute, Carnegie Mellon University website: http://www.sei.cmu.edu/library/abstracts/reports/87tr046.cfm
CHI:
Nestor, John, Evolving Persistent Objects in a Distributed Environment (CMU/SEI-87-TR-046 ). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1987. http://www.sei.cmu.edu/library/abstracts/reports/87tr046.cfm
MLA:
Nestor, J., 1987. Evolving Persistent Objects in a Distributed Environment (Technical Report CMU/SEI-87-TR-046 ). Pittsburgh: Software Engineering Institute, Carnegie Mellon University. http://www.sei.cmu.edu/library/abstracts/reports/87tr046.cfm
For more information