The resolver and the multi-interface still have problems.
Ref. "Issue 35" in the archive.

Daniel's work on this didn't really fix anything. But as it seems made the
multi-interface blocking while connecting to every IP except the 1st.
AFAICS (blocks in CURLM_STATE_WAITCONNECT).

multi-single (+ some traces) using the infamous misconfigured Dutch host
http://ubr4-ca5-0-sec.landg1.lb.home.nl:

> multi-single.exe
HANDLE 00B0A228: State: 0
HANDLE 00B0A228: State: 1
HANDLE 00B0A228: State: 2
....
HANDLE 00B0A228: State: 2
* About to connect() to ubr4-ca5-0-sec.landg1.lb.home.nl port 80
* Trying 10.243.112.1... HANDLE 00B0A228: State: 3
HANDLE 00B0A228: State: 3
HANDLE 00B0A228: State: 3
....
HANDLE 00B0A228: State: 3
* Connection failed
* Trying 82.73.204.1... * Connection refused << blocking here and below
* Trying 217.121.93.1... * Connection refused
* Trying 217.122.53.1... * Connection refused
* Trying 217.123.132.1... * Connection refused
* Trying 10.221.110.1... * Timed out << !! blocks for approx 15 sec here
* Trying 82.72.140.1... * Connection refused
* Closing connection #0

------------------------------

I don't understand the logic in Curl_is_connected(), seems trynextip() doesn't
do the right thing. Someone please try the modified multi-single.c attached.
Sorry, Daniel. I'd fix it myself if I had the time.

--gv