Message254389
I had a similar issue with ucspi-ssl that was fixed by following
the O'Reilly book's recommendations w.r.t WANT_READ/WANT_WRITE
with non-blocking sockets to the letter.
The recommendations are quite complex since apparently
WANT_READ/WANT_WRITE mean different things depending
on whether they occur *during a read* or *during a write*.
I haven't used Python's SSL module much: Since those flags
are exposed on the Python level, are users supposed to take
care of the above issues themselves for non-blocking sockets? |
|
Date |
User |
Action |
Args |
2015-11-09 14:28:20 | skrah | set | recipients:
+ skrah, janssen, pitrou, giampaolo.rodola, christian.heimes, alex, nikratio, dstufft |
2015-11-09 14:28:20 | skrah | set | messageid: <1447079300.54.0.791775602833.issue22499@psf.upfronthosting.co.za> |
2015-11-09 14:28:20 | skrah | link | issue22499 messages |
2015-11-09 14:28:20 | skrah | create | |
|