-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeout drop doesn't work since Jan 02, 2013 commit by LloydPickering #85
Comments
I see the problem here. The old code depending on the semaphore, the new code does not (async based). We do have a cleanup thread, but it doesn't pay attention to the timeout. I'll see if I can whip up a pull request to do that. |
(I think you are write on nuget not being updated from github) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem is that server never drops clients after timeout. What's interesting, it worked with nugget package of Alchemy WebSockets, but when I cloned git repo and compile last commit from master I noticed timeout never drops. Seems nugget package compiled not from the latest version?
bdefe79 - is the last commit that works correctly with timeout. After there was a lot of changes in WebSocketsServer.cs, especially in OnRunClient method
The text was updated successfully, but these errors were encountered: