This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author exarkun
Recipients amaury.forgeotdarc, barry, ddvoinikov, exarkun, giampaolo.rodola, janssen, josiah.carlson, josiahcarlson, qwavel, rhettinger, srid
Date 2009-10-15.18:49:23
SpamBayes Score 8.8919e-06
Marked as misclassified No
Message-id <>
Antoine asked me to give my opinion on the non-blocking SSL API.  I can
say that the current behavior of SSLSocket.recv is certainly not very
good and probably makes SSLSocket useless for any non-blocking
application.  Letting the underlying want-read/want-write error bubble
up to the caller definitely makes more sense than blocking.

I haven't had a chance to look into the new SSL code in depth, so don't
construe this as a thorough review of the change, though.
Date User Action Args
2009-10-15 18:49:25exarkunsetrecipients: + exarkun, barry, rhettinger, josiahcarlson, amaury.forgeotdarc, janssen, giampaolo.rodola, josiah.carlson, ddvoinikov, srid, qwavel
2009-10-15 18:49:25exarkunsetmessageid: <>
2009-10-15 18:49:24exarkunlinkissue3890 messages
2009-10-15 18:49:23exarkuncreate