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 pitrou
Recipients Arfrever, flox, giampaolo.rodola, janssen, jcea, pitrou, vstinner
Date 2010-04-08.20:15:09
SpamBayes Score 1.7314185e-06
Marked as misclassified No
Message-id <1270757714.55.0.481463036937.issue8108@psf.upfronthosting.co.za>
In-reply-to
Content
My analysis of SSL_shutdown() was missing something: timeout sockets are really non-blocking sockets in disguise. I guess it's never too late to notice.

OpenSSL doesn't know about the timeout, so we have to do it ourselves. Ironically, the infrastructure is already in place in _ssl.c, and used for read() and write() methods.

So here is a new patch, taking this into account.
History
Date User Action Args
2010-04-08 20:15:14pitrousetrecipients: + pitrou, jcea, janssen, vstinner, giampaolo.rodola, Arfrever, flox
2010-04-08 20:15:14pitrousetmessageid: <1270757714.55.0.481463036937.issue8108@psf.upfronthosting.co.za>
2010-04-08 20:15:10pitroulinkissue8108 messages
2010-04-08 20:15:10pitroucreate