Called by any Player/thread to add a sub-session to a session. It will switch the local heap to that of the peer before performing operations on the session pointer. It is essential that the session lock is used around this call. CSubSessionIx::Lock CSubSessionIx::UnLock

The PitBoss monitors the Comms Configurator sequence level and when the core components have been configured (this includes ESock) this method is called to delete any data structures used only during startup of ESock. CConfigurationLevelMonitor CPitBoss::iPendingIntroResponses

Used during binding when the PitBoss receives a introduction response message from a worker. The PitBoss will set-up housekeeping datastructures for the worker and add the supported protocols to its list of protocol pairings. TWorkerMsg::EMainIntroductionResp

Called by any Player/thread to remove a sub-session from a session. It will switch the local heap to that of the peer before performing operations on the session pointer. It is essential that the session lock is used around this call. CSubSessionIx::Lock CSubSessionIx::UnLock

Resolve a PlayerRole to its thread id (module names are far less volatile than thread assignments which in the future may become highly dynamic. So module names are used to couple tier ids to threads

Resolve a Worker thread's CFModule name to its thread id (module names are far less volatile than thread assignments which in the future may become highly dynamic. So module names are used to couple tier ids to threads

Immediate shutdowns expose a number of additional race risks; in the face of one happening to any thread at all we stop attempting certain kinds of cleanup. This should be acceptable behaviour since at it will be the whole of ESock shutting down. To avoid races between the testing and setting of this state, testing for it gains a lock which must be explicitly released. CPitBoss::ReleaseImmediateShutdownPresent()

Tests whether immediate shutdown is signaled. This function does not lock and is used where this knowledge is desired but no action is taken that might race with other threads. CPitBoss::TestAndLockImmediateShutdownPresent() CPitBoss::ReleaseImmediateShutdownPresent()

Monitor configuration level to know when it is safe to delete data used solely during startup/binding. Note that if we should support loading new Socket Server modules at run time, sometime after system start, this will need to be changed so the list is always available to new modules.

This is used by Worker threads (as well as ESock_Main) during immediate shutdown. As a Worker could potentially delete a sub-session at the same time as the Dealer trying to mark it orphaned, these two operations need to be protected during immediate shutdown (but not normally).

Set ETrue when immediate shutdown is received from the RootServer.

Session/subsession unique id counter. This value represents a next (free) id that will be assigned to a newly created CWorkerSubSession object.

Set ETrue when all Worker threads have finished tidying up during a shut down procedure. The ESock_Main instance will only shut down when this is ETrue.

Incremented when a request to bind to another instance has been received and decremented when a binding is complete. When the reference configurator configuration level have reached the point signifying that all core components have been configured and this TInt is 0, it is safe to delete data structures used only during startup. OnCoreComponentsConfigured()

Set ETrue when immediate shutdown is received by ESock_Main from the RootServer or if optional/graceful shutdown has been received at some point and the last session is closed.

ETrue if the PitBoss is in the process of shutting down. Set when optional or graceful shutdown is received by ESock_Main from the RootServer.