-
Notifications
You must be signed in to change notification settings - Fork 10
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
Incoming Connection Handling Needs to be Fixed #11
Comments
It might be possible to use the SocketServer Python Module to fix this fairly easily. |
Ahh, this is why there is this random down time. |
You should move to an async lib like gevent or Twisted if you feel serious about it. |
@Plausibility - agreed, we need something more "robust". My commit was just meant to be a quick fix. |
@JosephRedfern: It wouldn't be a small update, you'd probably be rewriting a significant amount of core code - the only bit which would stay reasonably similar would be how your commands are dispatched to classes. |
@Plausibility - I was suggesting that #12 is a quick fix, with your suggestion of gevent/Twisted being something more long-term. |
Definitely worth looking into, since as demonstrated, a non-closed socket can hang the entire operation. |
The current socket listen loop doesn't send the data off to a thread until it receives data. If you open a socket to the Bloocoin server and don't send any data, it blocks the main thread indefinitely. This creates a very simple DoS vulnerability.
The text was updated successfully, but these errors were encountered: