Open Client applications can function in two different session models that control how the client and AppServer interact:
Session-managed — The client maintains a dedicated physical connection to a single AppServer that handles each request for a given application service. In this session model, the client and AppServer share a common and persistent connection context over which run-time state can be maintained for the duration of the connection. Therefore, this session model is ideally suited for applications that must manage a large and complex transaction scope that includes multiple requests between the client and the AppServer.
Session-free — The client maintains a logical connection to a given application service, and each client request for that application service can be handled by any one of many
AppServer resources (that is, one or more AppServers and one or more AppServer agents of any one AppServer) that support the given application service. In this session model, the client shares no persistent connection context with any one AppServer resource. Each client request can execute on a different AppServer and on a different agent of any one AppServer. This session model supports maximum availability of AppServer resources. Therefore, this session model is ideally suited for applications that require maximum upward scalability and a transaction scope of no more than a single client request.
