Open perara opened 10 years ago
Hi there, Could you add the following to your server code before wssv.Start();
?
wssv.KeepClean = false;
Hello
This seems to work perfectly!
Is this a intended behaviour?
Thanks!
Is this a intended behaviour?
Nope. I have another workaround, so plz wait for a short while. Thx!
+1
Is this workaround still needed? I am running into the same issue on .NET Core 2.1.
Good Morning STA!
I'm getting the following exception after approx 60 seconds of my client running:
I'm connecting with the collowing code
And my server looks like this:
I logged duration of the connection three times, and i got the following timings: 57835ms First run 56207ms Second run 57343ms Third run
I'm not sure if this is something with websocket-sharp, but maybe you know the problem? :+1: