Managing stateless connection context

On a state-reset or state-aware AppServer, all remote procedures executed over the same connection run in the same AppServer agent. The state-aware AppServer session is dedicated to the client connection and its state at the initiation of a client request is exactly as it was when the previous request on the client connection finished.

Stateless AppServer sessions generally require more complex management than sessions on a state-reset or state-aware AppServer. The trade-off is potentially higher throughput for the effort. Because any AppServer agent in a stateless AppServer pool can handle any remote procedure request for any unbound connection, the context created by one remote procedure request is generally unavailable to the next request in the connection sequence. To help you manage context in a stateless environment, the AppServer provides the following mechanisms:

Other than in Using the SERVER-CONNECTION-BOUND attribute, most of the remaining information on context management applies only to AppServers running in stateless operating mode.

To support context management for both state-free and (unbound) stateless operating modes, OpenEdge provides the ClientContextId property on the Progress.Lang.OERequestInfo class. For more information, see Managing state-free and stateless client context.