Managing context for bound and unbound session-managed connections

On a bound session-managed connection, all remote procedures run in the session of a PAS for OpenEdge instance. The context at the initiation of a client request is exactly as it was when the previous request from the same client completed.

Unbound session-managed connections generally require more complex context management than for bound connections. The trade-off is potentially higher throughput for the effort. Because any ABL session in a PAS for OpenEdge session pool can handle any remote procedure request on any unbound connection, the context created by one remote procedure request is generally unavailable to the next request in the same connection sequence. To help you manage context for an unbound session-managed connection, OpenEdge provides the following ABL elements:

Other than in Using the SERVER-CONNECTION-BOUND attribute, most of the remaining information on context management applies only to session-managed connections in the unbound state.

To support context management for either session-free or unbound session-managed connections, OpenEdge also provides the ClientContextId property on the Progress.Lang.OERequestInfo class. For more information, see Managing client context for session-free and unbound session-managed connections.