Message102641
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. |
|
Date |
User |
Action |
Args |
2010-04-08 20:15:14 | pitrou | set | recipients:
+ pitrou, jcea, janssen, vstinner, giampaolo.rodola, Arfrever, flox |
2010-04-08 20:15:14 | pitrou | set | messageid: <1270757714.55.0.481463036937.issue8108@psf.upfronthosting.co.za> |
2010-04-08 20:15:10 | pitrou | link | issue8108 messages |
2010-04-08 20:15:10 | pitrou | create | |
|