Skip to content
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

closing client sockets timeout on attempts, #5

Open
technocake opened this issue Feb 24, 2012 · 0 comments
Open

closing client sockets timeout on attempts, #5

technocake opened this issue Feb 24, 2012 · 0 comments

Comments

@technocake
Copy link
Contributor

The client threads should really close the sockets after a timeout, so that blocking clients wont hang.

Problem: If a client speaking to the server is blocking, the NerdHandler will hang to. All the way until the client closes the connection.
The control of the socket should be on the server side, not the challenge side.

Solution:
A) Implement a timeout for each NerdHandler, and kill the NerdHandler after f.ex: 2s

For killing a thread, see:
http://mail.python.org/pipermail/tutor/2001-June/006702.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant