3.1.1.1 Global.Handle

The following ADM element is maintained by the server for each session context.

Global.Handle: Some methods on this interface require session context handle information to be stored on the server and used across multiple interface calls for a long duration of time. For these method calls, this protocol is stateful. The server stores this session context information and provides a session context handle (the Global.Handle ADM element) to the client to make subsequent interface calls by using this same session context information.

The server keeps a list of all active sessions and their associated session context information. Each session context is identified by a Global.Handle ADM element. After a session context has been established, a client can access messaging resources through this session context. The server keeps track of all open resources or any state information specific to the session on the session context. This can include but is not limited to resources, such as folders, messages, tables, attachments, streams, associated asynchronous context handles, and notification callbacks.

The server isolates all resources associated with one session context from all other session contexts on the server. Access to resources on one session context is not allowed using a session context handle of another session context.

When the session context handle is destroyed or the client connection is lost, the session context and all session context information is destroyed, all open resources are closed, and all Server objects that are associated with the session context are released.