Message104204
> That's what I thought at first too. But the user's sockets were set to
> blocking.
If you set a timeout on a socket, it is really non-blocking internally (from the OS' point of view). So perhaps this is what you are witnessing.
By the way, rather than sleeping a fixed amount of time before retrying, you could probably use select() on the socket. |
|
Date |
User |
Action |
Args |
2010-04-26 09:48:49 | pitrou | set | recipients:
+ pitrou, mdcowles, exarkun, neologix |
2010-04-26 09:48:48 | pitrou | set | messageid: <1272275328.66.0.51017590771.issue8493@psf.upfronthosting.co.za> |
2010-04-26 09:48:47 | pitrou | link | issue8493 messages |
2010-04-26 09:48:47 | pitrou | create | |
|