> From: Hu, Eric
> Sent: Wednesday, January 12, 2011 10:34 AM
> Subject: RE: axTLS patch set
>
> 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.

I'm wondering how much added code and complexity non-blocking support
would actually entail? An extra 2-5%, maybe? Couldn't this be supported
as a compile-time option when building axTLS?

We've used libcurl+axTLS for several years, and I don't recall ever
seeing a failure due to this. In fact, when we use HTTPS, it is used
as a logon transaction which is forwarded by the server to another
authentication server, and if the credentials are invalid, the
authentication server won't respond for 30 seconds, and when it does,
the HTTPS successfully completes, without any peep from axTLS.

We've also been using the multi interface for a couple of years,
together with axTLS, so this is all a rather unpleasant surprise
at this point.

Again, thanks for all of your efforts on this!

Gary @ Broadsoft

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-01-12