Shared Event ConnStateChange

ConnStateChange Event
Windows - Visual C++

Description
The ConnStateChange event is fired when the connection state has been changed. The application can display this for user, or inhibit actions when the connection is not ready.

DispId 0x04

Syntax
void OnConnStateChange(long NewState);

NewsState

Description

1: STARTSTATE

No login information yet. Application (or OCXCONN) must provide login name, password and server name. Transitions: Container Automatic: to ReadyToConnect (if login name, password and server name are available). Container manual: to TryToConnect (by calling Logon) or ReadyToConnect (by calling ShowLogon).

2: READY

In this state the program can respond to requests for headlines, stories, etc. Transistions: Container manual: to Disconnect (by calling Disconnect). NSI: to Fault or Timeout.

3: TERMINALSTATE

Unrecoverable. User must exit program. Transitions: none.

4: READYTOCONNECT

We have login information and can call Connect. Normally goes to this state after Disconnect also. Transitions: Container manual: to TryToConnect (by calling Connect).

5: TRYTOCONNECT

Transitions: Container automatic: to WaitingForConnect or TerminalState.

6: WAITINGFORCONNECT

Transitions: NSI: to Connected or StartState or TerminalState.

7: CONNECTED

Not necessarily ready to open views. Transitions: Container automatic: to Ready.

8: FAULT

Transitions: Container manual: to Disconnect (by calling Disconnect). Container Automatic: to FaultDelaying, FaultRestart, or Disconnect.

9: TIMEOUT

Transitions: Container manual: to Disconnect (by calling Disconnect). Container Automatic: to TimeoutDelaying, TimeoutRestart, or Disconnect.

10: DISCONNECT

Transitions: Container automatic: to Disconnecting.

11: DISCONNECTING

Transitions: NSI: to ReadyToConnect.

12: FAULTTRANSFER

Transitions: Container automatic: to FaultTransferring.

13: FAULTRESTART

Transitions: Container automatic: to FaultRestarting.

14: TIMEOUTTRANSFER

Transitions: Container automatic: to TimeoutTransferring.

15: TIMEOUTRESTART

Transitions: Container automatic: to TimeoutRestarting.

16: FAULTTRANSFERRING

Application can put up "Cancel transfer" dialog. Transitions: NSI: to Connected, Follower, Fault, or Timeout. Container manual: to Disconnect (by calling Disconnect) or Fault (by calling CancelAction). Container automatic: to Fault.

17: FAULTRESTARTING

Application can put up "Cancel restart" dialog. Transitions: NSI: to Connected, Follower, Fault, or Timeout. Container manual: to Disconnect (by calling Disconnect) or Fault (by calling CancelAction). Container automatic: to Fault.

18: TIMEOUTTRANSFERRING

Application can put up "Cancel transfer" dialog. Transitions: NSI: to Connected, Follower, or Timeout. Container manual: to Disconnect (by calling Disconnect) or Timeout (by calling CancelAction). Container automatic: to Timeout.

19: TIMEOUTRESTARTING

Application can put up "Cancel restart" dialog. Transitions: NSI: to Connected, Follower, or Timeout. Container manual: to Disconnect (by calling Disconnect) or Timeout (by calling CancelAction). Container automatic: to Timeout.

20: FAULTDELAYING

The client should delay before restarting. Transitions: Container automatic: to FaultRestart.

21: TIMEOUTDELAYING

Transitions: Container automatic: to TimeoutRestarting.

22: FOLLOWER

To handle the case where multiple COMs are active to the same connection. This session has no control of failover and can only follow what the controlling one does. Transitions: None in this release. NSI transitions to Connected, ReadyToConnect, or TerminalState.

Back to: Alert Events Connect Events Headline Events Quote Events

NewsState	Description
1: STARTSTATE	No login information yet. Application (or OCXCONN) must provide login name, password and server name. Transitions: Container Automatic: to ReadyToConnect (if login name, password and server name are available). Container manual: to TryToConnect (by calling Logon) or ReadyToConnect (by calling ShowLogon).
2: READY	In this state the program can respond to requests for headlines, stories, etc. Transistions: Container manual: to Disconnect (by calling Disconnect). NSI: to Fault or Timeout.
3: TERMINALSTATE	Unrecoverable. User must exit program. Transitions: none.
4: READYTOCONNECT	We have login information and can call Connect. Normally goes to this state after Disconnect also. Transitions: Container manual: to TryToConnect (by calling Connect).
5: TRYTOCONNECT	Transitions: Container automatic: to WaitingForConnect or TerminalState.
6: WAITINGFORCONNECT	Transitions: NSI: to Connected or StartState or TerminalState.
7: CONNECTED	Not necessarily ready to open views. Transitions: Container automatic: to Ready.
8: FAULT	Transitions: Container manual: to Disconnect (by calling Disconnect). Container Automatic: to FaultDelaying, FaultRestart, or Disconnect.
9: TIMEOUT	Transitions: Container manual: to Disconnect (by calling Disconnect). Container Automatic: to TimeoutDelaying, TimeoutRestart, or Disconnect.
10: DISCONNECT	Transitions: Container automatic: to Disconnecting.
11: DISCONNECTING	Transitions: NSI: to ReadyToConnect.
12: FAULTTRANSFER	Transitions: Container automatic: to FaultTransferring.
13: FAULTRESTART	Transitions: Container automatic: to FaultRestarting.
14: TIMEOUTTRANSFER	Transitions: Container automatic: to TimeoutTransferring.
15: TIMEOUTRESTART	Transitions: Container automatic: to TimeoutRestarting.
16: FAULTTRANSFERRING	Application can put up "Cancel transfer" dialog. Transitions: NSI: to Connected, Follower, Fault, or Timeout. Container manual: to Disconnect (by calling Disconnect) or Fault (by calling CancelAction). Container automatic: to Fault.
17: FAULTRESTARTING	Application can put up "Cancel restart" dialog. Transitions: NSI: to Connected, Follower, Fault, or Timeout. Container manual: to Disconnect (by calling Disconnect) or Fault (by calling CancelAction). Container automatic: to Fault.
18: TIMEOUTTRANSFERRING	Application can put up "Cancel transfer" dialog. Transitions: NSI: to Connected, Follower, or Timeout. Container manual: to Disconnect (by calling Disconnect) or Timeout (by calling CancelAction). Container automatic: to Timeout.
19: TIMEOUTRESTARTING	Application can put up "Cancel restart" dialog. Transitions: NSI: to Connected, Follower, or Timeout. Container manual: to Disconnect (by calling Disconnect) or Timeout (by calling CancelAction). Container automatic: to Timeout.
20: FAULTDELAYING	The client should delay before restarting. Transitions: Container automatic: to FaultRestart.
21: TIMEOUTDELAYING	Transitions: Container automatic: to TimeoutRestarting.
22: FOLLOWER	To handle the case where multiple COMs are active to the same connection. This session has no control of failover and can only follow what the controlling one does. Transitions: None in this release. NSI transitions to Connected, ReadyToConnect, or TerminalState.