Guido van Rossum wrote: >>The point is that in the standard case, a byte on the network is a byte >>in the application, so you either get a byte or you time out in the >>specified time. >> >>In the SSL case, you could neither get a byte nor time out, at the >>application layer, until much, much later than you thought you specified. >> >>This seems broken to me, and POLA would suggest I'm right (i.e. if I say >>time out in 1 second, I'll be pretty astonished when that turns into a day). > > > Any buffering scheme built on top of recv() has this problem. Tough. OK, so long as we're clear on the failure mode, its fine by me. Cheers, Ben. -- http://www.apache-ssl.org/ben.html http://www.thebunker.net/ "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4