3.2.1 Abstract Data Model

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 facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with the behavior that is described in this document.

Note that the abstract data model can be implemented in a variety of ways. This protocol does not prescribe or advocate any specific implementation technique.

The facet MUST extend the definition of the State field of the TIP connection object as specified in section 3.1.1.2 to include the following values:

• State: An enumeration that indicates what state the TIP connection is in. This field MUST be set to one of the values in the extended enumeration. The following are the extension values:

  • Idle Push: The TIP connection is waiting for a reply to a PUSH TIP command sent while in the Idle state.

  • Idle Reconnect: The TIP connection is waiting for a reply to a RECONNECT TIP command sent while in the Idle state.

  • Enlisted: The TIP connection is associated with a transaction object and will send TIP commands to notify its partner transaction manager of the transaction's outcome.

  • Enlisted Prepare: The TIP connection is waiting for a reply to a PREPARE TIP command sent while in the Enlisted state.

  • Enlisted Commit: The TIP connection is waiting for a reply to a COMMIT TIP command sent while in the Enlisted state.

  • Enlisted Abort: The TIP connection is waiting for a reply to an ABORT TIP command sent while in the Enlisted state.

  • Prepared: The transaction associated with the TIP connection has completed Phase 1.

  • Prepared Commit: The TIP connection is waiting for a reply to a COMMIT TIP command sent while in the Prepared state.

  • Prepared Abort: The TIP connection is waiting for a reply to an ABORT TIP command sent while in the Prepared state.