Author janssen
Recipients amaury.forgeotdarc, barry, ddvoinikov, exarkun, giampaolo.rodola, janssen, josiah.carlson, josiahcarlson, qwavel, srid
Date 2009-10-01.00:29:21
SpamBayes Score 1.56121e-09
Marked as misclassified No
Message-id <4b3e516a0909301729t5eda0bfej7493e71c147e215e@mail.gmail.com>
In-reply-to <1254253653.38.0.148741514276.issue3890@psf.upfronthosting.co.za>
Content
On Tue, Sep 29, 2009 at 12:47 PM, Giampaolo Rodola'
<report@bugs.python.org>wrote:

>
> Giampaolo Rodola' <billiejoex@users.sourceforge.net> added the comment:
>
> Uhm... I'm sorry but actually I'm not sure about this patch anymore.
> Now that I look at ssl.py again I'm noticing that send() is trapped in a
> "while True" loop as well and the patch doesn't cover it.
>
> Not sure if that has been added recently or it was already there at the
> time I submitted the report but it's another thing that need to be
> fixed.
>
>
> Moreover, I'm sure that removing the "while" loop is good for non-
> blocking sockets but what about blocking ones?
> Are SSL_ERROR_WANT_READ and SSL_ERROR_WANT_WRITE supposed to be raised
> in a blocking environment?
>

No.

> If they aren't then the current patch just needs to take care of send()
> method too, then it's fine.
>

Yes, it's fine.

Bill
Files
File name Uploaded
unnamed janssen, 2009-10-01.00:29:19
History
Date User Action Args
2009-10-01 00:29:28janssensetrecipients: + janssen, barry, josiahcarlson, exarkun, amaury.forgeotdarc, giampaolo.rodola, josiah.carlson, ddvoinikov, srid, qwavel
2009-10-01 00:29:21janssenlinkissue3890 messages
2009-10-01 00:29:21janssencreate