0.9.5

all platforms, I also edited a few data types slightly to prevent my
compiler from warning on comparisions between signed and unsigned values

fine..

host:port, so accessing curl.haxx.se on port 80 would yield a key value
of ::
curl.haxx.se:80

now.

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

Curl_write().

cases where EWOULDBLOCK or equivalent is returned. We must not block.

again. THIS IS NOT A NICE FIX.

again. THIS IS NOT A NICE FIX. We should/must make a select() then and only
retry when we can write to the socket again.

would crash. This corrects the problem.

over to non-blocking sockets, but this loops very nastily. We should return
back to the select() and wait there until more data arrives, not just blindly
attempt again and again...

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 :)

Set-Cookie: line was ignored if they didn't end with a trailing
semicolon. This is indeed wrong syntax, but there are high-profile web sites
out there sending cookies like that so we must make a best-effort to parse
them.

platforms, unrelated to what they might prefer by default

    - 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

expect (nor read) any response-body

cookie list, even though they're not supposed to do that...

I also replaced all printf() calls with calls to Curl_failf()

platforms that have such a function.
This affects multi-thread running libcurls on IPv4 systems that have VERBOSE
switched on. The previous version was risking that another thread overwrote
the data before it was read out in this thread. There could possibly also
be a slight risk that the data isn't zero terminated for a short while and
thus could cause the thread to crash...

header directory but the function *is* present!

to become properly 8-byte aligned on 64-bit archs. Philip Gladstone reported.