A network connection has been established to the Liberator. StreamLink will now attempt to log in to the Liberator session.
A connection attempt is in progress. If the connection attempt is successful, a
CONNECTED state will be raised, if the connection fails, the FAILED
event will be raised.
StreamLink has failed to retrieve the credentials.
StreamLink has successfully retrieved the credentials.
Disconnected from the Liberator. When this state is raised by the StreamLink library
all subscriptions have removed. StreamLink will not perform any activity until you
call connect() on the StreamLink object.
The client has been ejected from the Liberator. StreamLink will not perform any
more connection attempts and will switch to the DISCONNECTED state.
A connection attempt has failed. StreamLink will attempt to connect to a Liberator on the configured server list.
The client is now logged into the Liberator. In this state it is possible for StreamLink applications to receive subscription updates and receive responses to commands.
The client could not login to the Liberator. StreamLink will not perform any
more connection attempts and will switch to the DISCONNECTED state.
The connection to the Liberator has been lost. StreamLink will attempt to connect and establish a new session with a configured Liberator.
The Liberator session has been reconnected. This should be treated as an informational
event, StreamLink will switch to the LOGGEDIN state to simplify implementation
of your application (see the traffic light example above).
StreamLink is attempting to obtain a set of credentials to log in to the server.
A connection to the Liberator is not possible due to no network being available.
Generated using TypeDoc
Name
ConnectionState