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.

to compile libcurl stuff without any prior knowledge:

cc=`curl-config --cc`
cflags=`curl-config --cflags`
libs=`curl-config --libs`

$cc $flags $libs -o example example.c

Or if you prefer, the oh-so-cool single-line version:

`curl-config --cc --cflags --libs` -o example example.c

on unix-like systems

reporting bugs

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...

that it won't create an empty file if the remote file doesn't exist

ranges

unsigned everywhere

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

connection timeout