On Wed, 12 Jan 2011, Hu, Eric wrote:
We don't currently have a way to build libcurl without the multi interface
so it'd take a little work to get that going. Of course it would further
decrease the footprint...
A smaller footprint use would be awfully nice for us. Any idea if memory
usage would be reduced as well?
I doubt we'd see any noticable difference.
The socket is always set non-blocking within libcurl so that won't help us!
Really? (I suppose I could just look at the code) I'm surprised the easy
interface worked then. If the axTLS code sees "read" return -1, it assumes
the connection is lost, even if errno==EAGAIN. Maybe all of my tests were
with very fast servers that responded very quickly.
Well, most (all?) of the easy interface does recv after having done select on
the socket to figure out if there's a chance of anything to read so quite
possibly it never causes a problem...
--
/ daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
