3.17.1 Abstract Data Model

  • Article

This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to explain how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document.

The server maintains the data structures specified in section 3.9.1. In addition, the server maintains the following:

  • A table of objects, keyed by the activity ID.

  •  An activity timer for each activity.

  •  An activity lock.

  •  For each object, the causality identifier of the current outstanding ORPC call into the object, if any.