huge send buffer sizes

persistent connection. Mentioned by Immanuel Gregoire on the mailing list.

forwarded from the Gentoo bug tracker by Daniel Black and was originally
submitted by Robin Johnson, pointed out that libcurl would do bad memory
references when it failed and bailed out before the handler thing was
setup. My fix is not done like the provided patch does it, but instead I
make sure that there's never any chance for a NULL pointer in that struct
member.

This also defines it for WinCE even though it is a subset of WIN32.

out that SFTP requests didn't use persistent connections. Neither did SCP
ones.  I gave the SSH code a good beating and now both SCP and SFTP should
use persistent connections fine. I also did a bunch for indent changes as
well as a bug fix for the "keyboard interactive" auth.

ahost are ws2_32.lib and advapi32.lib

while () => while()
and some other minor re-indentings

callbacks needed to pass a buffer to the user.  Instead one per byte it
is now as little as one per segment.

out a problem in curl.h when building C++ apps with MSVC. To fix it, the
inclusion of header files in curl.h is moved outside of the C++ extern "C"
linkage block.

consistency

and if () so the rule is from now on => no space before the parenthesis.

connectdata struct. This will in theory enable us to do persistent connections
with SCP+SFTP, but currently the state machine always (and wrongly) cleanup
everything in the 'done' action instead of in 'disconnect'. Also did a bunch
of indent fixes, if () => if() and a few other source cleanups like added
comments etc.

happened when a user had a home dir as an empty string. curl would then do
free() on a wrong area.

due to a missing header file.

protocols listed in curl --version

always, except when --without-libssh2 was given

headers <winlap.h> and <winber.h> defines wrong calling convention.