New PR for #19(Watchdog terminates the driver when debugging longer than 10s)

[DarkNebula0]

Fix for SteamVR quits when debugging SlimeVR server for more than 10 seconds

• Rebased with new changes
• Wrapped linux socket client

@Eirenliel New PR for #19

[funnbot]

I thought this is what the --keepalive flag when launching vrserver is for.

Also, I'm not positive on the windows implementation for the bridge, but the linux one was written to be non-blocking, so wrapping it in a thread is fine, but doesn't do much.

On the windows side, isn't there an option to set a timeout instead of blocking to wait for messages? Using a thread is better, I'm just curious.

[DarkNebula0]

I thought this is what the --keepalive flag when launching vrserver is for.

Also, I'm not positive on the windows implementation for the bridge, but the linux one was written to be non-blocking, so wrapping it in a thread is fine, but doesn't do much.

On the windows side, isn't there an option to set a timeout instead of blocking to wait for messages? Using a thread is better, I'm just curious.

As far as I know there is no flag, you could use SetCommTimeouts or change the pipes to Overlapped(Event based), but you would have to do that in SlimeServer as well.

When I wrote it there was no linux implementation implemented. But it's been a few months :)

https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-setcommtimeouts