From 7751756636a786bcbe3ae543cec9318370ddeea3 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 14 Aug 2001 11:04:58 +0000 Subject: CURL_GLOBAL_WIN32 updates --- docs/curl_easy_init.3 | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'docs/curl_easy_init.3') diff --git a/docs/curl_easy_init.3 b/docs/curl_easy_init.3 index 60dd336f4..5c4a8c122 100644 --- a/docs/curl_easy_init.3 +++ b/docs/curl_easy_init.3 @@ -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 @@ -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 @@ -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! -- cgit v1.2.3