Author dabeaz
Recipients beazley, dabeaz, gregory.p.smith, loewis, ned.deily, pitrou, rosslagerwall, roysmith
Date 2011-01-13.14:10:29
SpamBayes Score 0.000105855
Marked as misclassified No
Message-id <1294927832.04.0.431521575126.issue7322@psf.upfronthosting.co.za>
In-reply-to
Content
Have any other programming environments ever had a feature where a socket timeout returns an exception containing partial data?    I'm not aware of one offhand and speaking as a systems programmer, something like this might be somewhat unexpected.

My concern is that in the presence of timeouts, the programmer will be forced to reassemble the message themselves from fragments returned in the exception.  However, one reason for using readline() in the first place is precisely so that you don't have to do that sort of thing.

Is there any reason why the input buffer can't be preserved across calls?   You've already got a file-like wrapper around the socket.  Just keep the unconsumed buffer in that instance.
History
Date User Action Args
2011-01-13 14:10:32dabeazsetrecipients: + dabeaz, loewis, beazley, gregory.p.smith, roysmith, pitrou, ned.deily, rosslagerwall
2011-01-13 14:10:32dabeazsetmessageid: <1294927832.04.0.431521575126.issue7322@psf.upfronthosting.co.za>
2011-01-13 14:10:29dabeazlinkissue7322 messages
2011-01-13 14:10:29dabeazcreate