Package	com.lightstreamer.as_client.events
Class	public class StatusChangeEvent
Inheritance	StatusChangeEvent LSClientEvent flash.events.Event

Dispatched whenever the connection status changes. A status change may be originated either by a custom action (e.g. by calling "openConnection") or by an internal action.

The normal cases are the following:

• After issuing "openConnection" or "openPollingConnection", the status switches to CONNECTING first; as soon as the new session is established, it will switch to STREAMING or POLLING respectively.
• After issuing "closeConnection", the status always switches to DISCONNECTED.
• In case of a server connection refusal, the status may switch from CONNECTING directly to DISCONNECTED. Before that, however, a ServerErrorEvent would be received.

Possible special cases are the following:

• In case of Server unavailability during streaming, the status may switch from STREAMING to STALLED. If the unavailability ceases, the status will switch back to STREAMING; otherwise, if the unavailability persists, the status will switch to CONNECTING and eventually to STREAMING.
• In case the connection or the whole session is forcibly closed by the Server, the status may switch from STREAMING or POLLING directly to DISCONNECTED. Before that, however, a ConnectionDropEvent would be received.
• In case the streaming connection is broken, the status may switch from STREAMING to CONNECTING and eventually to STREAMING. The same may happen for the POLLING status because of any problem during an intermediate poll.
• Because of the Stream-sense algorithm, the status may switch from CONNECTING to POLLING even in case "openConnection" was issued. Then, depending on the ConnectionPolicy.setBufferedStreamingHandled setting, it might directly switch to STREAMING.

Note the following caveats:

• In case of connection problems while the status is CONNECTING, connection retries may occur with no change in the status.
• If "openConnection" or "openPollingConnection" is issued when the current status is CONNECTING, no status change is notified. The same holds when "closeConnection" is issued and the current status is DISCONNECTED.
• If "openConnection" is issued and a session is active, it is closed first, even if it is already a streaming session; anyway, the status switches directly to CONNECTING. A similar consideration holds for "openPollingConnection".
• As soon as a successful streaming connection can be established, the Stream-sense algorithm is disabled for future connection attempts.

By setting a custom handler it is possible to perform actions related to connection and disconnection occurrences. Such actions can be issued directly inside a handler (e.g. to prevent an automatic reconnection attempt).

See also

---