95a1afb84b
As per http://docs.python.org/2/howto/sockets.html#using-a-socket it's possible that a socket recv() call returns 0 bytes if the remote closes the connection. In that case, recv() does not obey settimeout(): it just doesn't block and returns zero bytes immediately, which in this case results in an infinite loop if the transmission was incomplete. |
||
---|---|---|
.. | ||
bitmessageqt | ||
images | ||
pyelliptic | ||
socks | ||
translations | ||
addresses.py | ||
api_client.py | ||
bitmessagemain.py | ||
build_osx.py | ||
class_addressGenerator.py | ||
class_outgoingSynSender.py | ||
class_receiveDataThread.py | ||
class_sendDataThread.py | ||
class_singleCleaner.py | ||
class_singleListener.py | ||
class_singleWorker.py | ||
class_sqlThread.py | ||
defaultKnownNodes.py | ||
helper_bitcoin.py | ||
helper_bootstrap.py | ||
helper_generic.py | ||
helper_inbox.py | ||
helper_sent.py | ||
helper_startup.py | ||
highlevelcrypto.py | ||
message_data_reader.py | ||
proofofwork.py | ||
shared.py | ||
singleton.py | ||
tr.py |