CURLE_COULDNT_RESOLVE_PROXY and CURLE_COULDNT_RESOLVE_HOST on resolving
errors (as documented).

runtime libs.

protocol sockets even if the resolved address may say otherwise

have this check done on far too many places by now...

for Windows, that could lead to an Access Violation when the multi interface
was used due to an issue with how the resolver thread was and was not
terminated.

VS2005.

from url.c: Curl_disconnect().

The tag 'before_ftp_statemachine' was set just before this commit in case
of future need.

CURLE_OK or CURLE_OUT_OF_MEMORY.
Add typecast in hostares.c.

GetCurrentProcess() twice; use a local variable.

Added Traian Nicolescu's patches for threaded resolver on
Windows. Plugged some potential handle and memory leaks.

Refs.
  http://curl.haxx.se/mail/lib-2004-10/0134.html
  http://curl.haxx.se/mail/lib-2004-10/0157.html

of typecasts all over

linked list for name resolved data, even on hosts/systems with only IPv4
stacks as this simplifies a lot of code.

a host name that resolves to multiple IP addresses.

memory.h is included everywhere for this.

all things up to work with encoded host names internally, as well as keeping
'display names' to show in debug messages. IDN resolves work for me now using
ipv6, ipv4 and ares resolving. Even cookies on IDN sites seem to do right.

usage.