Author kristjan.jonsson
Recipients ggenellina, gregory.p.smith, gvanrossum, kristjan.jonsson
Date 2009-02-02.15:58:10
SpamBayes Score 1.12012e-06
Marked as misclassified No
Message-id <1233590293.19.0.669028207783.issue4448@psf.upfronthosting.co.za>
In-reply-to
Content
I have looked at this for py3k.
the behaviour of HTTPResponse.fp.read() is the same, wheter fp is 
buffered or not:  a read() will read to EOF for HTTP/1.1, which means 
blocking indefinetely.  So, read() is forbidden for HTTP/1.1.  For 
fp.read(n), buffered IO won't attempt to read more than is on the 
stream, if n bytes are avalible (SocketIO.read(N) will return a<N and 
not block) so there is no reason not to use buffering.
History
Date User Action Args
2009-02-02 15:58:13kristjan.jonssonsetrecipients: + kristjan.jonsson, gvanrossum, gregory.p.smith, ggenellina
2009-02-02 15:58:13kristjan.jonssonsetmessageid: <1233590293.19.0.669028207783.issue4448@psf.upfronthosting.co.za>
2009-02-02 15:58:11kristjan.jonssonlinkissue4448 messages
2009-02-02 15:58:10kristjan.jonssoncreate