Managing client context for session-free and unbound session-managed connections

In the session-free or the (especially unbound) session-managed application models of the PAS for OpenEdge instance, any available PAS for OpenEdge session handles each remote request from a PAS for OpenEdge client. The session can use a client context identifier provided by OpenEdge as a key to retrieve a previously initialized client context from a context store in order to execute the request on behalf of the originating client. On completion of the request, the agent can then update the client context in the context store for access by the client when the request returns, or (acting as a client) the session can make its own request to another PAS for OE instance, passing the same client context identifier on behalf of the original client.. Sessions across one or more PAS for OpenEdge instances can thus use this same client context identifier to access the context store on behalf of the original client request..

OpenEdge generates an initial, globally unique value for this client context identifier when it first creates the server object that a client uses to connect to a PAS for OpenEdge instance. The client can then assign its own value for this identifier if necessary, possibly one that has been previously initialized for a different PAS for OpenEdge connection.

For example, this identifier is typically used to identify the current user login session that a client initially establishes through a PAS for OpenEdge instance or OpenEdge PAS for OpenEdge instance that implements the authentication service for the client. This value is then propagated in subsequent requests sent between the client and any OpenEdge Application Server involved in requests for that same login session.