> To be safe(r), should we use the easy interface for HTTPS with axTLS, > instead of our current use of multi? I still can't believe we > haven't seen this issue pop up using multi. > Upon further investigation, I'm not sure it matters. I've been bouncing between axTLS versions 1.1.5 and 1.2.7. In the latter, it appears that fcntl (and its equivalent on Windows) is used to set reads back to blocking mode in ssl_client_new(). You can check to see if SOCKET_BLOCK is defined in your version's ssl/os_port.h. If so, the read operations are probably blocking.
While this might explain why you haven't seen any problems, it does seem to run counter to the spirit of the multi interface. Eric ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
