3.3.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 specification does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this specification.

The ADM for this interface is the same as that for the EMSMDB interface, as specified in section 3.1.1.

The AsyncEMSMDB uses an asynchronous Global.Handle ADM element, as defined in section 3.1.1.1. The Global.Handle ADM element maps to the session context that is associated with a session context handle. There is only one asynchronous Global.Handle ADM element for a session context.

All methods on the AsyncEMSMDB interface that use an asynchronous context handle are performed against the Session Context that is associated with the asynchronous Global.Handle ADM element (or asynchronous context handle).

The server keeps a mapping between the asynchronous Global.Handle ADM element and an active Session Context on the server. A Session Context can be created and destroyed through the EMSMDB interface.

When the Session Context is destroyed or the client connection is lost, the asynchronous context handle becomes invalid and will be rejected if used.