Feature Request: Automatic Keep-Alive

[nikeee]

See #64 for the need of this.

Option 1:

Use System.Timers.Timer Pros:

• Simple to implement
• Can be implemented external from the TeamSpeak client without breaking changes Cons:
• We currently target Net Standard 1.3 - there might not be a Timer available, so we have to bump the Net Standard version.

Note:

• Which Timer to use? See: https://jonskeet.uk/csharp/threads/timers.html
• We don't want to force the library user to use a specific one

Option 2:

Timeout in the response queue. Pros:

• KeepAlive will only be sent if there was no Cons:
• Harder to implement Note:
• Must be implemented in the QueryClient itself; if done correctly, would be transparent to the user

Option N

[your suggestion here (comment on this issue)]

General implementation notes:

• Some library users are have already implemented their own Keep-Alive logic.
• Design decision: Keep the query client / rich client dumb?

[Arefu]

Looks like I was wrong, Timers were introduced in .NET Standard 2.0.

I'll take a look at implementing it internally, I agree it should mostly be transparent, but there should be ways to disable it in case the user already has their own solution in place.

[Des1re7]

I have implemented this as a simple task:

private async Task KeepAlive(CancellationToken cancellationToken, TimeSpan delay)
{
    while (!cancellationToken.IsCancellationRequested)
    {
        await TeamSpeak.WhoAmI();
        await Task.Delay(delay, cancellationToken);
    }
}

[nikeee]

Solved via #67