when given in the curl_easy_setopt() and then parse them all on the first
curl_easy_perform() call instead.

case 306 added to verify that we do right

when talking to a IPv6-server using IPv6 IP address only.

proceed fine with the already existing options, just having a different
internal library default for capath.

working for "IPv6 enabled" libcurls yet, but should be pretty easy for
someone to adjust.

weren't used anyway and mostly caused confusion

the initial connect to "come through".

This should work fine for connect and for FTP-PASV connects. Needs massive
testing.

the easy interface, it CANNOT be used by a mixture.

for receiving data from the network. It is meant as a hint, not as a forced
limit.

variables, conditions and things.

message is supposed to be ignored.

sized buffer that may be passed to a write callback

we need to point to user-provided fd_sets

any name resolved data in any curl handle struct. That way, we won't mind
if the cache entries are pruned for the next time we need them. We'll just
resolve them again instead.

This changes the Curl_resolv() proto. It modifies the SessionHandle struct
but perhaps most importantly, it'll make the internals somewhat dependent
on the DNS cache not being disabled as that will cripple operations somewhat.
Especially for persistant connections.

CURLINFO_REDIRECT_TIME and CURLINFO_REDIRECT_COUNT.

CURLOPT_DEBUGFUNCTION and CURLOPT_DEBUGDATA.

this work-around is not needed anymore!

- made a separate buffer for uploads (due to the non-blocking stuff)
- added two connectdata struct fields for non-blocking uploads

2) in the curl_dns_cache_entry structure, timestamp should be
a time_t instead of an integer (although I doubt it matters).

The default cache timeout for this is 60 seconds, which is arbitrary and
completely subject to change :)

    - Use a global dns cache (via setting the tentatively named,
    CURLOPT_DNS_USE_GLOBAL_CACHE option to true)
    - Use a per-handle dns cache, by default
    - Use a pooled dns cache when in the "multi" interface

we return a set of headers not more. This enables FTP operations that don't
transfer any data, only perform FTP commands.

is not dealt with when we find an end-of-response line, as there might be
important stuff even after the correct line. So on subsequent invokes, the
cached data must be used!

attempting to use EPSV before the standard PASV.