Loading docs/curl_easy_init.3 +6 −4 Original line number Diff line number Diff line Loading @@ -2,7 +2,7 @@ .\" nroff -man [file] .\" $Id$ .\" .TH curl_easy_init 3 "5 March 2001" "libcurl 7.7" "libcurl Manual" .TH curl_easy_init 3 "14 August 2001" "libcurl 7.8.1" "libcurl Manual" .SH NAME curl_easy_init - Start a libcurl session .SH SYNOPSIS Loading @@ -17,8 +17,10 @@ intializes curl and this call MUST have a corresponding call to .I curl_easy_cleanup when the operation is complete. On win32 systems, you need to init the winsock stuff manually, libcurl will not do that for you. WSAStartup() and WSACleanup() should be used accordingly. On win32 systems, if you want to init the winsock stuff manually, libcurl will not do that for you. WSAStartup() and WSACleanup() should then be called accordingly. If you want libcurl to handle this, use the CURL_GLOBAL_WIN32 flag in the initial curl_global_init() call. Using libcurl 7.7 and later, you should perform all your sequential file transfers using the same curl handle. This enables libcurl to use persistant Loading @@ -27,6 +29,6 @@ connections where possible. If this function returns NULL, something went wrong and you cannot use the other curl functions. .SH "SEE ALSO" .BR curl_easy_cleanup "(3), " .BR curl_easy_cleanup "(3), " curl_global_init "(3) .SH BUGS Surely there are some, you tell me! docs/libcurl.3 +2 −2 Original line number Diff line number Diff line Loading @@ -2,7 +2,7 @@ .\" nroff -man [file] .\" $Id$ .\" .TH libcurl 5 "28 May 2001" "libcurl 7.8" "libcurl overview" .TH libcurl 5 "14 August 2001" "libcurl 7.8.1" "libcurl overview" .SH NAME libcurl \- client-side URL transfers .SH DESCRIPTION Loading Loading @@ -101,7 +101,7 @@ you to init the winsock stuff before you use the libcurl functions. Details on this are noted on the curl_easy_init() man page. (*) = it appears as if users of the cygwin environment get this done automatically. automatically, also libcurl 7.8.1 and later can handle this for you. .SH "THREADS" Never ever call curl-functions simultaneously using the same handle from several threads. libcurl is thread-safe and can be used in any number of Loading Loading
docs/curl_easy_init.3 +6 −4 Original line number Diff line number Diff line Loading @@ -2,7 +2,7 @@ .\" nroff -man [file] .\" $Id$ .\" .TH curl_easy_init 3 "5 March 2001" "libcurl 7.7" "libcurl Manual" .TH curl_easy_init 3 "14 August 2001" "libcurl 7.8.1" "libcurl Manual" .SH NAME curl_easy_init - Start a libcurl session .SH SYNOPSIS Loading @@ -17,8 +17,10 @@ intializes curl and this call MUST have a corresponding call to .I curl_easy_cleanup when the operation is complete. On win32 systems, you need to init the winsock stuff manually, libcurl will not do that for you. WSAStartup() and WSACleanup() should be used accordingly. On win32 systems, if you want to init the winsock stuff manually, libcurl will not do that for you. WSAStartup() and WSACleanup() should then be called accordingly. If you want libcurl to handle this, use the CURL_GLOBAL_WIN32 flag in the initial curl_global_init() call. Using libcurl 7.7 and later, you should perform all your sequential file transfers using the same curl handle. This enables libcurl to use persistant Loading @@ -27,6 +29,6 @@ connections where possible. If this function returns NULL, something went wrong and you cannot use the other curl functions. .SH "SEE ALSO" .BR curl_easy_cleanup "(3), " .BR curl_easy_cleanup "(3), " curl_global_init "(3) .SH BUGS Surely there are some, you tell me!
docs/libcurl.3 +2 −2 Original line number Diff line number Diff line Loading @@ -2,7 +2,7 @@ .\" nroff -man [file] .\" $Id$ .\" .TH libcurl 5 "28 May 2001" "libcurl 7.8" "libcurl overview" .TH libcurl 5 "14 August 2001" "libcurl 7.8.1" "libcurl overview" .SH NAME libcurl \- client-side URL transfers .SH DESCRIPTION Loading Loading @@ -101,7 +101,7 @@ you to init the winsock stuff before you use the libcurl functions. Details on this are noted on the curl_easy_init() man page. (*) = it appears as if users of the cygwin environment get this done automatically. automatically, also libcurl 7.8.1 and later can handle this for you. .SH "THREADS" Never ever call curl-functions simultaneously using the same handle from several threads. libcurl is thread-safe and can be used in any number of Loading
