Hi

I take this opportunity to ask: shouldn't we improve the interface of
getting the active socket even more?
What I suggested earlier [1] was to enable CURLINFO_LASTSOCK to retrieve
the "active" socket when called while the request is in progress, and
retrieve the last used socket if called when the request is done (and
the connection still exists). I guess that was discarded since it meant
to change an existing API.
But now we are introducing a new API that even has the word "active" in
its name, but also only works if the request is completely processed. I
plea to have a look at my patch again, and consider it to be adapted to
work with the new CURLINFO_ACTIVESOCKET while letting CURLINFO_LASTSOCK
unchanged.

cheers, Frank

[1] http://article.gmane.org/gmane.comp.web.curl.library/46025
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-08-25