You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
The text was updated successfully, but these errors were encountered: