> Here's an initial patch set to get axTLS working with cURL.  This code
> doesn't yet pass all the HTTPS tests.  There are two (311, 312) that
> will require more detailed error-reporting from axTLS, but the others
> (301, 306, 313, 560) should be readily fixed in cURL.
> 
Regarding test 560 (use of axTLS with the multi interface), it turns out that 
axTLS does not support non-blocking read/write operations.  According to Cam 
(axTLS maintainer) this is by design to keep the binary footprint and memory 
use to an absolute minimum.  The easiest thing to do is just note somewhere in 
the docs that axTLS does not support the multi interface.  The other extreme is 
to have the multi interface turned off when "--with-axtls" is specified in the 
configure line.  Perhaps a happy medium is to have axtls.c notice when an FD is 
non-blocking.  Any preferences?  Other ideas about how to deal with this?

Thanks,
Eric
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html

Reply via email to