The ULC client reconnect feature assigns a token to each context. This token is used during reconnect to find the contexts. Normally these are the contexts which belong to the user who just tries to reconnect. Therefore this token is normally a unique identifier for a user (i.e. user ID). However the token can also contain other information such as an application name.
Every client reconnect token strategy must be a subclass of the abstract class UlcReconnectTokenStrategy and is responsible for creating and handling the token of a context. It is up to the (infrastructure) programmer to implement such a strategy. A company would normally use one single strategy for all ULC applications. Specific strategies can be implemented for administrative and maintenance purposes (e.g. a strategy that allows a super user to reconnect to any hanging context).
The following strategies are included in this release for demonstration and debugging purposes only. They should not be used in production code.