Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
77517566
Commit
77517566
authored
23 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
CURL_GLOBAL_WIN32 updates
parent
2de6d8ba
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/curl_easy_init.3
+6
-4
6 additions, 4 deletions
docs/curl_easy_init.3
docs/libcurl.3
+2
-2
2 additions, 2 deletions
docs/libcurl.3
with
8 additions
and
6 deletions
docs/curl_easy_init.3
+
6
−
4
View file @
77517566
...
...
@@ -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!
This diff is collapsed.
Click to expand it.
docs/libcurl.3
+
2
−
2
View file @
77517566
...
...
@@ -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
...
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment