3.1.2 Timers
The following timers are used by this protocol.
SessionProtocolTimer: An independent timer for each Session object (section 3.1.1.4), which causes the Session object to time out if its State is not Ready.
-
The legal range for the SessionProtocolTimer timeout value is 8-60 seconds.<5>
OOBConnectorProtocolTimer: An independent timer for each OOB Connector object, which is started each time an OOB Connector object State transitions into WaitingForTransmit or WaitingForACK. If the timer fires before the object State transitions to Ready, the protocol is incomplete and the object State transitions to Incomplete.
-
The legal range for the OOBConnectorProtocolTimer timeout value is 8-60 seconds.<6>
-
The following timers illustrate abstract data model object lifetime issues, but they are not necessary in all implementations:
OOBConnectorKeepAliveTimer: An independent timer for each OOB Connector object (section 3.1.1.2), which is started each time an OOB Connector object State transitions into Incomplete. If it fires before the object State transitions out of Incomplete, the initialization reference SHOULD be released.<7> If there are no other references to the object, the object is destroyed.
SessionFactoryKeepAliveTimer: An independent timer for each Session Factory object (section 3.1.1.3), which is started when a Session Factory object is created. If it fires before a client takes ownership of the object, the Session Factory object SHOULD BE deleted.<8>