The OpenEdge Hive

Bruce Gruenbaum:
Session Management and Context Management are closely related but subtly different. A client may have many connections to several different targets. Each of those connections may be termed a session and its lifetime is the duration of the connection. That is a physical session. Many times though, the client makes repeated connections to a target and often to more than one target at a time. It may often be possible to reduce the amount of processing time involved by reusing an authentication token. Thus a logical session may span many connections to many different targets. The Session Manager is responsible of tracking data that is related to the logical session.

Thomas Mercer-Hursh
My own inclination would be to think of a session as the duration of an AVM instance, regardless of what happened to connections since one could have all sorts of interesting complexities like:

1. connect to A
2. connect to B
3. disconnect from A
4. disconnect from B

Perhaps one also wants to have a session-connection instance, one per.

And, for a client, if they are connecting to a state free AppServer, there will be many many connections during one session.

Initial content adapted from an exchange on PEG.