to verify winsock API availability.

using winsock or winsock2 API.

resolving is completed so we must make sure to survive it and mark the
connection as async (ie not yet connected completely).

ever actually are used

could very well cause a negate number get passed in and thus cause reading
outside of the array usually used for this purpose.

We avoid this by using the uppercase macro versions introduced just now that
does some extra crazy typecasts to avoid byte codes > 127 to cause negative
int values.

#1579171

even when using curl_multi_socket() or even using the multi_perform() when
relying on multi_timeout() to be good.

c-ares name resolves, but now we do!

to the CURLOPT_DEBUGFUNCTION callback has been fixed (it was erroneously
included as part of the header).  A message was also added to the
command line tool to show when data is being sent, enabled when
--verbose is used.

for it

function, this is only meant to allow easier tracking of the internal handle's
state and what sockets they use. Only for research and development.

to a multi stack will cause CURLM_BAD_EASY_HANDLE to get returned.

and while doing so it became apparent that the current timeout system for
the socket API really was a bit awkward since it become quite some work to
be sure we have the correct timeout set.

Jeff then provided the new CURLMOPT_TIMERFUNCTION that is yet another
callback the app can set to get to know when the general timeout time
changes and thus for an application like hiperfifo.c it makes everything a
lot easier and nicer. There's a CURLMOPT_TIMERDATA option too of course in
good old libcurl tradition.

anymore

case 535 and it now runs fine. Again a problem with the pipelining code not
taking all possible (error) conditions into account.

In this way 304 tests out of 304 reported OK.

now runs fine.