C# | Visual Basic | Visual C++ |
public interface IConnectionConfiguration
Public Interface IConnectionConfiguration
public interface class IConnectionConfiguration
All Members | Properties | ||||
Icon | Member | Description |
---|---|---|
HeartbeatInterval |
Gets or sets the number of milliseconds between heartbeat latency messages.
| |
Name |
Gets the name that identifies the connection details.
| |
NoopInterval |
Gets or sets the number of seconds between Noop commands.
See Remarks in IConnectionConfiguration.
| |
NoopTimeout |
Gets or sets the timeout period (in seconds) for detecting the loss of
the connection to Liberator.
See Remarks in IConnectionConfiguration.
| |
ReconnectAttempts |
Gets or sets the number of reconnect attempts that will be made to each server.
| |
ReconnectInterval |
Gets or sets the reconnect interval.
| |
SyncInitialSpacing |
Gets or sets the time in milliseconds between successive sync messages, until the first SyncSize messages have been sent to Liberator.
For further information, see Clock Offset and Latency Measurement.
| |
SyncSize |
Gets or sets the number of sync messages that StreamLink uses to calculate the clock offset between
Liberator and StreamLink.
For further information, see Clock Offset and Latency Measurement.
| |
SyncSpacing |
Gets or sets the time in milliseconds between successive sync messages, after the first SyncSize messages have been sent to Liberator.
For further information, see Clock Offset and Latency Measurement.
|
StreamLink uses the RTTP Noop ("no operation") command internally to check that the connection to the Liberator is still present. It sends a Noop command to the Liberator every NoopInterval seconds. When the connection is operating normally, Liberator will send back a response to the Noop command. StreamLink assumes that the connection is lost if it does not receive the response within NoopTimeout seconds, and if it has not received any data from Liberator within that time.
Reconnection settings determine how StreamLink behaves when reconnecting, or whether reconnection is attempted at all.
StreamLink can also use sync and heartbeat messages to calculate the clock offset and latency between Liberator and StreamLink. For further information, see Clock Offset and Latency Measurement.