fix printf-style format strings

Chris Conroy's RTSP followup fixes

fix compiler warning

  proxy that cannot be resolved when using c-ares. This matches the behaviour
  when not using c-ares.

fix compiler warning

HAVE_GETADDRINFO_THREADSAFE definition for non-configure win32 builds

add inclusion of curl_memory.h

adjust preprocessor symbol definition check relative to resolver specialty

from hostip.h to setup.h in order to allow proper inclusion in any file.

This represents no functional change at all in which resolver is used,
everything still works as usual, internally and externally there is no
difference in behavior.

s/RTPDATA/INTERLEAVEDATA/

removal of Curl_addrinfo_copy(), Curl_addrinfo6_callback(), and
Curl_addrinfo4_callback()

libcurl options for controlling what to get and how to receive posssibly
interleaved RTP data. Initial commit.

  HTTP Cookie: header _needs_ to be sorted on the path length in the cases
  where two cookies using the same name are set more than once using
  (overlapping) paths. Realizing this, identically named cookies must be
  sorted correctly. But detecting only identically named cookies and take care
  of them individually is harder than just to blindly and unconditionally sort
  all cookies based on their path lengths. All major browsers also already do
  this, so this makes our behavior one step closer to them in the cookie area.

  Test case 8 was the only one that broke due to this change and I updated it
  accordingly.

  again when downloading files over FTP using ASCII and it turns out that the
  final size of the file is not the same as the initial size the server
  reported. This is very common since servers don't take the newline
  conversions into account.

of messages atomic, on systems where an fwrite of a memory buffer is atomic.

maketgz already converts this file to DOS style with an awk filter.

much as possible in one go, as long as it doesn't block and hasn't reached the
end of the state machine.
This avoids spurious -1 returns from curl_multi_fdset() simply because
previously it would return from this function without anything in EWOUDLBLOCK
and thus basically it wasn't actually waiting for anything!!

state, we return CURLM_CALL_MULTI_PERFORM unconditionally then so that we
can act faster like in the case the protocol-specific connect doesn't block
on anything and we can just persue on the next action immediately. It also
then avoids a case where curl_multi_fdset() would return -1.

  interval even during very slow connects.