21.2. The object model, object state and recovery
Throughout Part III we have used an object model for reasoning about atomic transactions. In this chapter we focus on object state and how and when it is recorded in persistent memory. Clients of a TP system are not concerned with object state explicitly, but with the results of operation invocations. The TPS implementation must ensure that the states of the objects comprising the system together present a consistent system state to its clients.
In Section 19.9 we assumed that an object records all relevant information on the operations that are invoked on it, for example, the transaction identifier and time of invocation. In Chapter 20 this was used for concurrency control. We assumed, as a theoretical ...
Get Operating Systems: Concurrent and Distributed Software Design now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
