Hi Martin, On Tue, Nov 21, 2006 at 06:56:20AM +0100, "Martin v. L?wis" wrote: > Right: socket._fileobject will invoke recv as many times as > necessary to read the requested amount of data. I was somehow > assuming that it maps read() to read(2), which, in turn, would > directly map to recv(2), which could return less data. > > So it's a semantic change only for the last block. That means that it would be rather pointless to make the change, right? The original poster's motivation is to get accurate progress during the transfer - but he missed that he already gets that. The proposed change only appears to be relevant together with a hypothetical rewrite of the underlying code, one that would use recv() instead of read(). A bientot, Armin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4